mock-acme 0.1.0__tar.gz

mock_acme-0.1.0/CHANGELOG.md

@@ -0,0 +1,60 @@
+# Changelog
+
+Every release of [mock-acme](https://pypi.org/project/mock-acme/). The format
+follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the
+versions follow [semantic versioning](https://semver.org/spec/v2.0.0.html) -
+while the major version is 0, a minor bump may change behaviour, and each entry
+says so where it does.
+
+## [Unreleased]
+
+Nothing yet.
+
+## [0.1.0] - 2026-10-05
+
+The first release.
+
+### Added
+
+- **The integrations that lived in the mocks' `examples/` folders, in one
+  package** ([#1], [#4]). `mockacme.po_bridge` from mock-edi;
+  `mockacme.invoice_check` and `mockacme.remittance` from mock-sap;
+  `mockacme.pay_invoices`, `mockacme.payment_run`, `mockacme.procure_to_pay`
+  and the `mockacme.bank_messages` they share from mock-bank. Each mock has
+  removed its copy, starting with the release after mock-sap 0.17.1, mock-edi
+  0.7.0 and mock-bank 0.7.0. Anything that imported
+  `mockbank.examples.payment_run` imports `mockacme.payment_run` instead.
+- **Tests that start the three mocks themselves** ([#1]). Importing `tests`
+  starts mock-sap, mock-edi and mock-bank on ports the operating system chose,
+  so there is nothing to start first and no port to keep free.
+- **`payment_run`'s statement readers held to mock-bank's own writers**
+  ([#6]), with moov-io's BAI2 and NACHA sample files.
+
+### Changed
+
+These differ from the last copies the mocks carried.
+
+- **Money arriving is not posted to SAP as a payment coming back** ([#3]).
+  `payment_run` tells a returned payment from a received credit, and posts a
+  received credit without the reference it quotes, so that SAP does not reopen
+  a paid invoice. It records a problem on the run each time. This is a stopgap
+  until a `FINSTA01` can say which kind of credit a line is
+  (rseufert/mock-sap#89).
+- **A statement is posted to SAP in its own currency** ([#3]). The `FINSTA01`
+  carried EUR whatever the statement said. A statement that names no currency
+  is not posted, and the run says so. A BAI2 statement with no currency on the
+  account or the group is read as USD.
+
+### Known to be wrong
+
+- **A second payment run started before the bank's statement is posted pays
+  the same invoice again** ([#2]). SAP has no state between open and cleared
+  for a run to write (rseufert/mock-sap#90). A test states this behaviour so
+  that it stays visible.
+
+[0.1.0]: https://github.com/rseufert/mock-acme/releases/tag/v0.1.0
+[#1]: https://github.com/rseufert/mock-acme/pull/1
+[#2]: https://github.com/rseufert/mock-acme/issues/2
+[#3]: https://github.com/rseufert/mock-acme/pull/3
+[#4]: https://github.com/rseufert/mock-acme/pull/4
+[#6]: https://github.com/rseufert/mock-acme/pull/6

mock_acme-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 mock-acme contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

mock_acme-0.1.0/MANIFEST.in

@@ -0,0 +1,2 @@
+include LICENSE README.md CHANGELOG.md
+recursive-include tests *.py *.md *.txt *.ach

mock_acme-0.1.0/PKG-INFO

@@ -0,0 +1,161 @@
+Metadata-Version: 2.4
+Name: mock-acme
+Version: 0.1.0
+Summary: The integration between the mocks: the middleware that mock-sap, mock-edi and mock-bank exist to test. Zero dependencies.
+License: MIT
+Project-URL: Repository, https://github.com/rseufert/mock-acme
+Project-URL: Issues, https://github.com/rseufert/mock-acme/issues
+Project-URL: Changelog, https://github.com/rseufert/mock-acme/blob/main/CHANGELOG.md
+Keywords: sap,edi,x12,iso20022,procure-to-pay,reconciliation,integration,middleware,mock,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Topic :: Office/Business :: Financial
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: test
+Requires-Dist: mock-sap>=0.17.0; extra == "test"
+Requires-Dist: mock-edi; extra == "test"
+Requires-Dist: mock-bank; extra == "test"
+Dynamic: license-file
+
+# mock-acme
+
+**The integration between the mocks.** [mock-sap](https://github.com/rseufert/mock-sap),
+[mock-edi](https://github.com/rseufert/mock-edi) and
+[mock-bank](https://github.com/rseufert/mock-bank) stand in for systems you do
+not own, so that the code between them can be tested. This is that code: ACME's
+middleware, the fourth actor in every story the mocks tell.
+
+It is not a mock, and it is not a client library to put in front of real money.
+It is a reference: worked integrations, each with tests that run against the
+released mocks, kept in one place so that there is one copy of each.
+
+## What is here
+
+| Module | Carries | Between |
+| --- | --- | --- |
+| `mockacme.po_bridge` | a purchase order out as an 850, the 855 back as an ORDRSP IDoc | SAP, supplier |
+| `mockacme.invoice_check` | the supplier's 856 and 810, matched to the order, posted as an INVOIC IDoc or blocked | SAP, supplier |
+| `mockacme.pay_invoices` | a supplier's 810s, paid as a pain.001 and followed to the statement | supplier, bank |
+| `mockacme.payment_run` | SAP's open items, paid as a pain.001 or a NACHA file, cleared by posting the statement as a FINSTA01 | SAP, bank |
+| `mockacme.remittance` | SAP's payment advice (a PEXR2002 it generates) out as an 820, and what the supplier made of it | SAP, supplier |
+| `mockacme.procure_to_pay` | one purchase from the order to the cleared payment | all three |
+
+`mockacme.bank_messages` is what the two payment modules share: the call to the
+bank and the reading of its ISO 20022 answers.
+
+Every module talks to the mocks over HTTP and imports none of them. The package
+has no dependencies.
+
+## Installing
+
+```bash
+python3 -m pip install mock-acme
+```
+
+That installs the package and nothing else. The mocks it talks to are separate:
+`pip install mock-sap mock-edi mock-bank`.
+
+## Running the tests
+
+From a checkout:
+
+```bash
+python3 -m pip install -e ".[test]"
+python3 -m unittest discover -s tests -t . -v
+```
+
+That is the whole arrangement. Importing `tests` starts the three mocks, each on
+a port the operating system chose, and stops them afterwards.
+[`tests/__init__.py`](tests/__init__.py) says how to point the tests at a mock
+that is already running, which is how they are run against a mock's `main`.
+
+`tests/test_payment_run_readers.py` is the one test that imports a mock rather
+than talking to it: it gives `payment_run`'s hand-written statement readers the
+same statement mock-bank wrote as a `camt.053` and as BAI2, and five BAI2 files
+from [moov-io/bai2](https://github.com/moov-io/bai2), and holds them to
+mock-bank's own reader. The samples and their licence are in
+[`tests/samples/external/`](tests/samples/external/SOURCES.md).
+
+`payment_run` pays by ACH as well. The same tests in that mode:
+
+```bash
+PAYMENT_RUN_FORMAT=nacha python3 -m unittest -v tests.test_payment_run
+```
+
+The released mocks are what a pull request is tested against. A second
+workflow, [`mocks-main.yml`](.github/workflows/mocks-main.yml), runs the same
+tests every night against each mock's `main`, so that a change merged there
+which breaks this code is seen before it is released. It is not a required
+check; a red run there says something about another repository. To do the same
+by hand:
+
+```bash
+python3 -m pip install \
+  "mock-sap @ git+https://github.com/rseufert/mock-sap@main" \
+  "mock-edi @ git+https://github.com/rseufert/mock-edi@main" \
+  "mock-bank @ git+https://github.com/rseufert/mock-bank@main"
+```
+
+## Known to be wrong
+
+`payment_run` can pay an invoice twice: a second run started before the bank's
+statement has been posted selects the same invoice again, and the bank pays it
+again. SAP offers no state between open and cleared for a run to write
+([mock-sap#90](https://github.com/rseufert/mock-sap/issues/90)), so this is not
+fixed, and `tests/test_payment_run.py` has a test that says so. It is tracked
+in [#2](https://github.com/rseufert/mock-acme/issues/2).
+
+Money arriving is posted to SAP without the reference it quotes, so that SAP
+does not take it for a returned payment and reopen an invoice. That is a
+stopgap, said as a problem on the run each time it happens, until the FINSTA01
+has a way to tell the two apart
+([mock-sap#89](https://github.com/rseufert/mock-sap/issues/89)).
+
+## Releasing
+
+A release is the same three acts as in the mocks,
+by one person in one sitting: merge a pull request that sets `version` in
+`pyproject.toml` and `__version__` in `mockacme/__init__.py` and dates the
+section in [`CHANGELOG.md`](CHANGELOG.md); tag that commit `v<version>`; publish
+a GitHub Release from the tag. Publishing the Release runs
+[`publish.yml`](.github/workflows/publish.yml), which runs the tests, builds,
+refuses a tag that disagrees with the package, and uploads to PyPI through
+Trusted Publishing. Running that workflow by hand uploads to TestPyPI instead.
+
+There is no `tools/release.py` here as there is in the mocks: the steps are done
+by hand, and CI checks only that the two places the version is written agree.
+
+## Where the code came from
+
+The modules were copied on 2026-10-04 from the `examples/` folder of the mock
+each was written beside, with their tests; `remittance` was written there
+afterwards and followed on 2026-10-05. Nothing in them changed but imports,
+the lines saying how to run the tests, and issue references, which now name the
+repository they belong to.
+
+| Here | From | At |
+| --- | --- | --- |
+| `po_bridge`, its tests | mock-edi `examples/` | `0e86279` (0.7.0) |
+| `invoice_check`, its tests | mock-sap `examples/` | `0ea524d` |
+| `remittance`, its tests | mock-sap `examples/` | `73055a2` |
+| `bank_messages`, `pay_invoices`, `payment_run`, `procure_to_pay`, their tests | mock-bank `examples/` | `fd618e6` (0.7.0) |
+
+The originals were removed from those repositories on 2026-10-05, and each
+left an `examples/README.md` saying which file became which. This is the only
+copy.
+
+The repository's settings are described in [docs/GITHUB.md](docs/GITHUB.md).

mock_acme-0.1.0/README.md

@@ -0,0 +1,128 @@
+# mock-acme
+
+**The integration between the mocks.** [mock-sap](https://github.com/rseufert/mock-sap),
+[mock-edi](https://github.com/rseufert/mock-edi) and
+[mock-bank](https://github.com/rseufert/mock-bank) stand in for systems you do
+not own, so that the code between them can be tested. This is that code: ACME's
+middleware, the fourth actor in every story the mocks tell.
+
+It is not a mock, and it is not a client library to put in front of real money.
+It is a reference: worked integrations, each with tests that run against the
+released mocks, kept in one place so that there is one copy of each.
+
+## What is here
+
+| Module | Carries | Between |
+| --- | --- | --- |
+| `mockacme.po_bridge` | a purchase order out as an 850, the 855 back as an ORDRSP IDoc | SAP, supplier |
+| `mockacme.invoice_check` | the supplier's 856 and 810, matched to the order, posted as an INVOIC IDoc or blocked | SAP, supplier |
+| `mockacme.pay_invoices` | a supplier's 810s, paid as a pain.001 and followed to the statement | supplier, bank |
+| `mockacme.payment_run` | SAP's open items, paid as a pain.001 or a NACHA file, cleared by posting the statement as a FINSTA01 | SAP, bank |
+| `mockacme.remittance` | SAP's payment advice (a PEXR2002 it generates) out as an 820, and what the supplier made of it | SAP, supplier |
+| `mockacme.procure_to_pay` | one purchase from the order to the cleared payment | all three |
+
+`mockacme.bank_messages` is what the two payment modules share: the call to the
+bank and the reading of its ISO 20022 answers.
+
+Every module talks to the mocks over HTTP and imports none of them. The package
+has no dependencies.
+
+## Installing
+
+```bash
+python3 -m pip install mock-acme
+```
+
+That installs the package and nothing else. The mocks it talks to are separate:
+`pip install mock-sap mock-edi mock-bank`.
+
+## Running the tests
+
+From a checkout:
+
+```bash
+python3 -m pip install -e ".[test]"
+python3 -m unittest discover -s tests -t . -v
+```
+
+That is the whole arrangement. Importing `tests` starts the three mocks, each on
+a port the operating system chose, and stops them afterwards.
+[`tests/__init__.py`](tests/__init__.py) says how to point the tests at a mock
+that is already running, which is how they are run against a mock's `main`.
+
+`tests/test_payment_run_readers.py` is the one test that imports a mock rather
+than talking to it: it gives `payment_run`'s hand-written statement readers the
+same statement mock-bank wrote as a `camt.053` and as BAI2, and five BAI2 files
+from [moov-io/bai2](https://github.com/moov-io/bai2), and holds them to
+mock-bank's own reader. The samples and their licence are in
+[`tests/samples/external/`](tests/samples/external/SOURCES.md).
+
+`payment_run` pays by ACH as well. The same tests in that mode:
+
+```bash
+PAYMENT_RUN_FORMAT=nacha python3 -m unittest -v tests.test_payment_run
+```
+
+The released mocks are what a pull request is tested against. A second
+workflow, [`mocks-main.yml`](.github/workflows/mocks-main.yml), runs the same
+tests every night against each mock's `main`, so that a change merged there
+which breaks this code is seen before it is released. It is not a required
+check; a red run there says something about another repository. To do the same
+by hand:
+
+```bash
+python3 -m pip install \
+  "mock-sap @ git+https://github.com/rseufert/mock-sap@main" \
+  "mock-edi @ git+https://github.com/rseufert/mock-edi@main" \
+  "mock-bank @ git+https://github.com/rseufert/mock-bank@main"
+```
+
+## Known to be wrong
+
+`payment_run` can pay an invoice twice: a second run started before the bank's
+statement has been posted selects the same invoice again, and the bank pays it
+again. SAP offers no state between open and cleared for a run to write
+([mock-sap#90](https://github.com/rseufert/mock-sap/issues/90)), so this is not
+fixed, and `tests/test_payment_run.py` has a test that says so. It is tracked
+in [#2](https://github.com/rseufert/mock-acme/issues/2).
+
+Money arriving is posted to SAP without the reference it quotes, so that SAP
+does not take it for a returned payment and reopen an invoice. That is a
+stopgap, said as a problem on the run each time it happens, until the FINSTA01
+has a way to tell the two apart
+([mock-sap#89](https://github.com/rseufert/mock-sap/issues/89)).
+
+## Releasing
+
+A release is the same three acts as in the mocks,
+by one person in one sitting: merge a pull request that sets `version` in
+`pyproject.toml` and `__version__` in `mockacme/__init__.py` and dates the
+section in [`CHANGELOG.md`](CHANGELOG.md); tag that commit `v<version>`; publish
+a GitHub Release from the tag. Publishing the Release runs
+[`publish.yml`](.github/workflows/publish.yml), which runs the tests, builds,
+refuses a tag that disagrees with the package, and uploads to PyPI through
+Trusted Publishing. Running that workflow by hand uploads to TestPyPI instead.
+
+There is no `tools/release.py` here as there is in the mocks: the steps are done
+by hand, and CI checks only that the two places the version is written agree.
+
+## Where the code came from
+
+The modules were copied on 2026-10-04 from the `examples/` folder of the mock
+each was written beside, with their tests; `remittance` was written there
+afterwards and followed on 2026-10-05. Nothing in them changed but imports,
+the lines saying how to run the tests, and issue references, which now name the
+repository they belong to.
+
+| Here | From | At |
+| --- | --- | --- |
+| `po_bridge`, its tests | mock-edi `examples/` | `0e86279` (0.7.0) |
+| `invoice_check`, its tests | mock-sap `examples/` | `0ea524d` |
+| `remittance`, its tests | mock-sap `examples/` | `73055a2` |
+| `bank_messages`, `pay_invoices`, `payment_run`, `procure_to_pay`, their tests | mock-bank `examples/` | `fd618e6` (0.7.0) |
+
+The originals were removed from those repositories on 2026-10-05, and each
+left an `examples/README.md` saying which file became which. This is the only
+copy.
+
+The repository's settings are described in [docs/GITHUB.md](docs/GITHUB.md).

mock_acme-0.1.0/mock_acme.egg-info/PKG-INFO

@@ -0,0 +1,161 @@
+Metadata-Version: 2.4
+Name: mock-acme
+Version: 0.1.0
+Summary: The integration between the mocks: the middleware that mock-sap, mock-edi and mock-bank exist to test. Zero dependencies.
+License: MIT
+Project-URL: Repository, https://github.com/rseufert/mock-acme
+Project-URL: Issues, https://github.com/rseufert/mock-acme/issues
+Project-URL: Changelog, https://github.com/rseufert/mock-acme/blob/main/CHANGELOG.md
+Keywords: sap,edi,x12,iso20022,procure-to-pay,reconciliation,integration,middleware,mock,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Topic :: Office/Business :: Financial
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: test
+Requires-Dist: mock-sap>=0.17.0; extra == "test"
+Requires-Dist: mock-edi; extra == "test"
+Requires-Dist: mock-bank; extra == "test"
+Dynamic: license-file
+
+# mock-acme
+
+**The integration between the mocks.** [mock-sap](https://github.com/rseufert/mock-sap),
+[mock-edi](https://github.com/rseufert/mock-edi) and
+[mock-bank](https://github.com/rseufert/mock-bank) stand in for systems you do
+not own, so that the code between them can be tested. This is that code: ACME's
+middleware, the fourth actor in every story the mocks tell.
+
+It is not a mock, and it is not a client library to put in front of real money.
+It is a reference: worked integrations, each with tests that run against the
+released mocks, kept in one place so that there is one copy of each.
+
+## What is here
+
+| Module | Carries | Between |
+| --- | --- | --- |
+| `mockacme.po_bridge` | a purchase order out as an 850, the 855 back as an ORDRSP IDoc | SAP, supplier |
+| `mockacme.invoice_check` | the supplier's 856 and 810, matched to the order, posted as an INVOIC IDoc or blocked | SAP, supplier |
+| `mockacme.pay_invoices` | a supplier's 810s, paid as a pain.001 and followed to the statement | supplier, bank |
+| `mockacme.payment_run` | SAP's open items, paid as a pain.001 or a NACHA file, cleared by posting the statement as a FINSTA01 | SAP, bank |
+| `mockacme.remittance` | SAP's payment advice (a PEXR2002 it generates) out as an 820, and what the supplier made of it | SAP, supplier |
+| `mockacme.procure_to_pay` | one purchase from the order to the cleared payment | all three |
+
+`mockacme.bank_messages` is what the two payment modules share: the call to the
+bank and the reading of its ISO 20022 answers.
+
+Every module talks to the mocks over HTTP and imports none of them. The package
+has no dependencies.
+
+## Installing
+
+```bash
+python3 -m pip install mock-acme
+```
+
+That installs the package and nothing else. The mocks it talks to are separate:
+`pip install mock-sap mock-edi mock-bank`.
+
+## Running the tests
+
+From a checkout:
+
+```bash
+python3 -m pip install -e ".[test]"
+python3 -m unittest discover -s tests -t . -v
+```
+
+That is the whole arrangement. Importing `tests` starts the three mocks, each on
+a port the operating system chose, and stops them afterwards.
+[`tests/__init__.py`](tests/__init__.py) says how to point the tests at a mock
+that is already running, which is how they are run against a mock's `main`.
+
+`tests/test_payment_run_readers.py` is the one test that imports a mock rather
+than talking to it: it gives `payment_run`'s hand-written statement readers the
+same statement mock-bank wrote as a `camt.053` and as BAI2, and five BAI2 files
+from [moov-io/bai2](https://github.com/moov-io/bai2), and holds them to
+mock-bank's own reader. The samples and their licence are in
+[`tests/samples/external/`](tests/samples/external/SOURCES.md).
+
+`payment_run` pays by ACH as well. The same tests in that mode:
+
+```bash
+PAYMENT_RUN_FORMAT=nacha python3 -m unittest -v tests.test_payment_run
+```
+
+The released mocks are what a pull request is tested against. A second
+workflow, [`mocks-main.yml`](.github/workflows/mocks-main.yml), runs the same
+tests every night against each mock's `main`, so that a change merged there
+which breaks this code is seen before it is released. It is not a required
+check; a red run there says something about another repository. To do the same
+by hand:
+
+```bash
+python3 -m pip install \
+  "mock-sap @ git+https://github.com/rseufert/mock-sap@main" \
+  "mock-edi @ git+https://github.com/rseufert/mock-edi@main" \
+  "mock-bank @ git+https://github.com/rseufert/mock-bank@main"
+```
+
+## Known to be wrong
+
+`payment_run` can pay an invoice twice: a second run started before the bank's
+statement has been posted selects the same invoice again, and the bank pays it
+again. SAP offers no state between open and cleared for a run to write
+([mock-sap#90](https://github.com/rseufert/mock-sap/issues/90)), so this is not
+fixed, and `tests/test_payment_run.py` has a test that says so. It is tracked
+in [#2](https://github.com/rseufert/mock-acme/issues/2).
+
+Money arriving is posted to SAP without the reference it quotes, so that SAP
+does not take it for a returned payment and reopen an invoice. That is a
+stopgap, said as a problem on the run each time it happens, until the FINSTA01
+has a way to tell the two apart
+([mock-sap#89](https://github.com/rseufert/mock-sap/issues/89)).
+
+## Releasing
+
+A release is the same three acts as in the mocks,
+by one person in one sitting: merge a pull request that sets `version` in
+`pyproject.toml` and `__version__` in `mockacme/__init__.py` and dates the
+section in [`CHANGELOG.md`](CHANGELOG.md); tag that commit `v<version>`; publish
+a GitHub Release from the tag. Publishing the Release runs
+[`publish.yml`](.github/workflows/publish.yml), which runs the tests, builds,
+refuses a tag that disagrees with the package, and uploads to PyPI through
+Trusted Publishing. Running that workflow by hand uploads to TestPyPI instead.
+
+There is no `tools/release.py` here as there is in the mocks: the steps are done
+by hand, and CI checks only that the two places the version is written agree.
+
+## Where the code came from
+
+The modules were copied on 2026-10-04 from the `examples/` folder of the mock
+each was written beside, with their tests; `remittance` was written there
+afterwards and followed on 2026-10-05. Nothing in them changed but imports,
+the lines saying how to run the tests, and issue references, which now name the
+repository they belong to.
+
+| Here | From | At |
+| --- | --- | --- |
+| `po_bridge`, its tests | mock-edi `examples/` | `0e86279` (0.7.0) |
+| `invoice_check`, its tests | mock-sap `examples/` | `0ea524d` |
+| `remittance`, its tests | mock-sap `examples/` | `73055a2` |
+| `bank_messages`, `pay_invoices`, `payment_run`, `procure_to_pay`, their tests | mock-bank `examples/` | `fd618e6` (0.7.0) |
+
+The originals were removed from those repositories on 2026-10-05, and each
+left an `examples/README.md` saying which file became which. This is the only
+copy.
+
+The repository's settings are described in [docs/GITHUB.md](docs/GITHUB.md).

mock_acme-0.1.0/mock_acme.egg-info/SOURCES.txt

@@ -0,0 +1,35 @@
+CHANGELOG.md
+LICENSE
+MANIFEST.in
+README.md
+pyproject.toml
+mock_acme.egg-info/PKG-INFO
+mock_acme.egg-info/SOURCES.txt
+mock_acme.egg-info/dependency_links.txt
+mock_acme.egg-info/requires.txt
+mock_acme.egg-info/top_level.txt
+mockacme/__init__.py
+mockacme/bank_messages.py
+mockacme/invoice_check.py
+mockacme/pay_invoices.py
+mockacme/payment_run.py
+mockacme/po_bridge.py
+mockacme/procure_to_pay.py
+mockacme/remittance.py
+tests/__init__.py
+tests/test_invoice_check.py
+tests/test_pay_invoices.py
+tests/test_payment_run.py
+tests/test_payment_run_readers.py
+tests/test_po_bridge.py
+tests/test_procure_to_pay.py
+tests/test_remittance.py
+tests/samples/external/LICENSE-Apache-2.0.txt
+tests/samples/external/NOTICE-moov-ach.txt
+tests/samples/external/SOURCES.md
+tests/samples/external/bai2-sample1.txt
+tests/samples/external/bai2-sample2.txt
+tests/samples/external/bai2-sample3.txt
+tests/samples/external/bai2-sample4.txt
+tests/samples/external/bai2-sample5.txt
+tests/samples/external/nacha-return-WEB.ach

mock_acme-0.1.0/mock_acme.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

mock_acme-0.1.0/mock_acme.egg-info/requires.txt

@@ -0,0 +1,5 @@
+
+[test]
+mock-sap>=0.17.0
+mock-edi
+mock-bank

mock_acme-0.1.0/mock_acme.egg-info/top_level.txt

@@ -0,0 +1 @@
+mockacme

mock_acme-0.1.0/mockacme/__init__.py

@@ -0,0 +1,23 @@
+"""mock-acme: the integration between the mocks.
+
+ACME is the company in every story the mocks tell: the buyer that sends the
+purchase order, the SAP system that owes the invoice, the account the bank
+pays from. This package is ACME's middleware, the code that carries a document
+from one system to the next:
+
+    po_bridge       SAP purchase order -> 850 -> supplier; 855 -> SAP
+    invoice_check   856 and 810 from the supplier, matched to the order, posted to SAP
+    pay_invoices    810s from the supplier, paid through the bank
+    payment_run     SAP's open items, paid through the bank and cleared by its statement
+    remittance      SAP's payment advice -> 820 -> supplier
+    procure_to_pay  all of it, across all three mocks
+
+It is not a mock. mock-sap, mock-edi and mock-bank stand in for systems you do
+not own so that code like this can be tested; this is that code. It talks to
+them over HTTP and imports none of them.
+
+It is a reference, not a client library to put in front of real money:
+`payment_run` can still pay an invoice twice, in the way rseufert/mock-acme#2
+says. Standard library only.
+"""
+__version__ = "0.1.0"