Supplier and Invoice API
svc-supplier
Catalogue ag-ap-invoice
Invoice Settlement Sub Agent
Settles a single supplier invoice for the accounts payable orchestrator, one attested instance per invoice.
Catalogue: registered
Identity: issued
production
version 2.3.0
Held here, by the catalogue
Registration
- Catalogue id
- ag-ap-invoice
- Business unit
- Business Banking, Accounts Payable
- Legal entity
- Commonwealth Bank of Australia
- Division
- agentic
- Accountable owner
- Kirsten Yeo, Accounts Payable Product
- Version
- 2.3.0
- Environment
- production
- Repository
- https://github.com/commbank-agentic/ap-invoice-settler
- Software bill of materials
- sbom/ap-invoice-settler-2.3.0.cdx.json
- Risk assessment
- RA-2289
- Change reference
- CHG-4417
- Registered by
- Accounts Payable Product
- Parent agent
- ag-ap-orchestrator
None of this is in the Trust Controller, and none of it needs to be. This is what a catalogue is for.
Held elsewhere, by the Trust Controller
Identity
- Entity id
- https://agent-ap-invoice.demo.cba.raidiam.io
- Authorisation server
- CommBiz Identity Platform
- Capability role
- cba.agentic.invoice.settler
- May request
- supplier_invoiceaccounts_readpayment_initiation
- May move money
- yes, inside a delegated envelope
- Federation roles
- cba.oidc.participantcba.agentic.membercba.agentic.invoice.settlercba.payments.initiatorcba.supplier.reader
- Manufacturer
- CBA Agent Provider
- Signing key
- kms://cba-au/agentic/ap-invoice-settler
- Lifecycle state
- issued
Settles exactly one invoice, inside the amount and the window the orchestrator delegated. It can initiate the payment for that invoice and can never widen what it was given.
Published by the group against the capability role. The catalogue does not write it and cannot change it.
Shown here as a last known outcome. This app did not decide any of it, cannot change any of it, and would be misrepresenting the model if it implied otherwise.
What this agent calls
Integration
The protected resources this agent is built to reach. Being built to call a resource is not the same as being entitled to, which is what the capability role decides and the delegated envelope then narrows.
Payments API
svc-payments