Per-approver breakdown for the Payment Journal, with a Payment Run header that summarises totals per approver and per supplier.

  • Current version: v0.1.0.0
  • AL prefix: PAYME
  • Object range: 81700-81799
  • Business Central: 26.0.0.0
  • Publisher: Amplio Solutions Ltd

AMP Payment Approver Breakdown

Per-approver breakdown for the Payment Journal so the approver, treasury team or director can see — before posting — who is being paid, by whom approved, and the totals split per currency and bank account.
  • Publisher: Amplio Solutions Ltd
  • Object prefix: AMP
  • Object ID range: 81700..81799
  • Target: BC application 26.0.0.0 / platform 26.0.0.0 (runtime 14.0, country GB)
  • Version: 0.1.0.0 (MVP scaffold — step 1, see DevOps #2922)

What this does

Adds a Payment Approver Breakdown view over the standard Payment Journal that summarises proposed payments by:

  1. Approver — who authorised each line, with a per-approver total and count.
  2. Supplier — sub-totalled inside each approver group, so reviewers can spot the largest single-vendor exposure.
  3. Currency and Bank Account — totals are split per CCY and per outgoing bank account so multi-currency / multi-bank runs are readable.

The breakdown is read-only: it never mutates the underlying Payment Journal. It is intended as a pre-posting sanity check on payment runs, surfacing concentration risk and any approver who has approved more than the configured per-approver ceiling.


Folder layout

Amplio_Payment_Approver_Breakdown/
├── app.json
├── README.md
├── .gitignore
├── .editorconfig
├── .vscode/
│   └── launch.json                 # cloud sandbox launch profile
├── permissionset/                  # permission sets ship here
├── Translations/                   # .xlf files produced by AL compiler
└── src/
    ├── Codeunits/                  # business logic
    ├── Enums/                      # enum definitions
    ├── PageExtensions/             # extensions to standard pages (Payment Journal)
    ├── Pages/                      # the Approver Breakdown page
    ├── Queries/                    # aggregating queries that feed the breakdown
    ├── Reports/                    # optional printable summary
    ├── TableExtensions/            # extensions to Gen. Journal Line / Payment Journal Batch
    └── Tables/                     # Payment Run header + Payment Run Line cache

Folders are currently empty placeholders — the AL objects are added by the next build steps in the work-item series (#2923 onwards).


Build & deploy

This is a standard AL workspace. Open the folder in VS Code with the AL Language extension; symbols are downloaded against the AmplioDev cloud sandbox referenced in .vscode/launch.json. The .app artefact lands in the workspace root and is .gitignore'd.


AppSource-safe

  • Unique app ID (ca7349d3-2dda-40c1-9cc7-aff00a573625) — not shared with any other Amplio repo.
  • Object ID range carved out of Amplio's AppSource registration range (81700..81799).
  • "target": "Cloud" — no on-prem-only APIs.
  • Depends only on Base Application and System Application at 26.0.0.0.
  • resourceExposurePolicy set the same as the rest of the Amplio MVP scaffolds (debug + source download enabled for internal review; tightened before AppSource submission).

Change log

See CHANGELOG.md.