How it works

From ERP to Payment Certificate, one chain.

Every figure moves forward through a single, forward-only chain. Nothing is re-typed between stages, so the certificate is always a faithful reflection of the cost beneath it.

  1. ERP → SOCC01

    Extract & standardise

    Pull cost data from COINS, JDE, SAP, Oracle or Insite — via API or file — and map every line into one standardised SOCC schema, reconciled against the general ledger.

  2. Payment Workflow02

    Assemble the Defined Cost

    Open a payment period, profile-populate costs, and allow or disallow each line. The SCC Defined Cost grid and rules engine make each decision explicit and auditable.

  3. Build-up03

    Roll up to the amount due

    The build-up summary carries allowed Defined Cost through fee, disallowed cost and prior payments to the amount due this period — no re-keying, no spreadsheet drift.

  4. E-AFP Certificate04

    Issue the certificate

    The Interim Payment Certificate is reproduced as live modules — Stage A/B/C waterfall and a digital signatory chain that certifies the figures and produces a shareable bundle.

  5. Finance05

    Raise the invoice & release payment

    The certified amount flows into invoicing and the payment gate, with interest accrual on late payment — closing the loop from raw cost to released funds.

Walk the chain with your own contract.