Substantiate the availability
your team reports.

Start with one receivables-only USD facility and one reporting entity. Agree the measurement dates, full ledger population, eligibility rules, debtor identity mapping, concentration basis, advance rates, reserves, commitment and usage. Independently work the borrowing base, signed availability and submitted-certificate comparisons for each date.

The synthetic example’s 25% debtor concentration cap, 80% advance, aging limits and reserve are demonstration terms. None becomes a customer default. Unsupported material provisions return a not-ready decision or a separately qualified scope; they are not omitted.

Inventory, broader collateral categories, customer integration, legal lien verification, automatic monitoring, lender submission and planning are outside the starting scope. Additional support must be explicitly agreed and verified.

1. Appoint accountable owners. A treasury or controllership owner leads evaluation, supported by the designated agreement reviewer and security team. Obtain legal review where your process requires it.
2. Provide the reviewed agreement. Include signed terms and amendments, clause-to-rule interpretation, collateral scope, deductions, exceptions and independent reference workings.
3. Reconcile the source records. Prepare the complete receivable ledger and control balance, stable debtor identities, invoice and due dates, applied cash/credits, eligibility evidence, reserve, principal, LC usage and submitted certificate. Reconcile sources using the agreed independent evidence.
4. Approve processing and acceptance. Agree environment, providers, access roles, retention, deletion and evidence exports before sharing company data. Qualify the actual import path and agreement calculation. Freeze the test cases, timetable, fee and customer effort allowance before kickoff.

The readiness assessment returns a ready or not-ready decision. A field mapping or successful synthetic calculation alone does not establish customer readiness.

These are proposed criteria to agree before results, not customer outcomes or service guarantees.

Reconciled coverage

The declared ledger reconciles to control totals, with zero unexplained monetary difference. Duplicate, missing, contradictory and unsupported records produce the agreed rejection or incompleteness result.

Exact calculation

Every accepted case matches the independent reference workings and certificate comparison with zero unexplained discrepancy. Include concentration, reserve, commitment, signed availability and one-cent boundary cases.

Meaningful adverse cases

Exercise unresolved eligibility, a disputed exclusion, overadvance, a matching certificate that reports overadvance and a differing certificate with positive availability. A correct adverse result can pass correctness without establishing process value.

Enforced review

Changed records require fresh preparation and approval. Stale or forged approval is rejected; previews remain conditional. Approval authorizes analysis only.

Reviewer-led evidence

Your reviewer completes the agreed repeat review and traces the calculation to sources and treatment without an AGX engineer editing records or code. Count all assistance. Reopening and downloads retain the original reviewed version.

Quote readiness work, implementation needs, pilot delivery and customer preparation separately. Agree a fixed delivery fee, timetable and effort allowance after reviewing the agreement and source package. No unspecified onboarding effort is assumed to be zero.

Measure first-use and repeat-cycle preparation/review effort against your existing process. Report calculation and human review time separately, with failures and assistance retained. Freeze the process-value target and measurement method before results; require a customer-approved cost case.

Your sponsor accepts or rejects the scorecard against the agreed criteria. Wider use requires separate qualification of the actual data path, roles, deployment, retention, recovery and operating ownership. Synthetic evidence does not establish enterprise security certification or production readiness.

Review the synthetic ABL study