Customer Payment & Statement Portal

The problem you are actually paying for

In most Dynamics 365 Finance & Operations deployments the accounts receivable team spends its week doing clerical work: re-sending PDF invoices, exporting an ad-hoc statement into Excel because the customer says they never received one, chasing which of eleven open invoices a lump-sum bank transfer was meant to cover, and manually applying settlements against CustTrans after the fact. None of this is accounting. It is email routing.

The customer's side is no better. A buyer who wants to check what is outstanding has to phone your AR clerk. A buyer who wants to pay today has no route to do so except a wire with a free-text reference that your team will later have to decode. Every day of that friction is a day of DSO you are financing.

F&O has the ledger. What it does not ship is an external, customer-facing surface over it. That surface is what ECOSIRE builds for you.

What ECOSIRE builds

This is a build-to-order engagement. Nothing here is a pre-packaged download — we scope your AR process, then write and deliver the extension against your environment.

X++ extension in F&O (no overlayering)

All server-side work is delivered as a versioned X++ extension model: extension classes, Chain of Command on the standard customer and settlement classes, table and form extensions, and new tables for portal-specific state (payment intents, portal users, statement runs, audit trail). We do not overlayer standard objects, so your One Version updates stay clean and your LCS deployable package continues to build without conflict resolution.

The read surface: what the customer sees

Open transactions are read through purpose-built data entities exposed over OData, scoped so a portal session can only ever see its own CustTable account and its own CustTrans rows. Typical surfaces:

• Open invoice list with due date, currency, original amount and remaining amount, driven from customer open transactions.
• Aged balance view aligned to your existing aging period definition so the portal number and the internal aging report agree.
• On-demand customer account statement generation, rendered from the standard SSRS report or a purpose-built layout, delivered as a PDF the customer downloads themselves.
• Invoice document retrieval, pulling the archived print of the free text or sales invoice rather than regenerating it.

The write surface: payment and settlement

The portal never writes directly to the ledger from a web session. A customer action creates a payment intent record in the extension's own table. A batch job then picks it up and does the accounting work inside F&O using the standard settlement APIs — creating the customer payment journal line, marking the selected transactions for settlement, and posting through the standard journal posting path so number sequences, ledger dimensions, exchange rate handling and financial period validation all behave exactly as they do for a manually keyed payment.

That separation matters: it means a portal outage or a browser refresh can never leave a half-posted journal, and every posted line is traceable back to the intent record that created it.

Payment provider integration

We integrate the payment provider you already use or select — the portal redirects or hosts the provider's session, and the provider's webhook confirms capture before any settlement is attempted. Settlement is idempotent against the provider's transaction reference, so a duplicated webhook cannot double-apply a payment. Partial payments, over-payments and on-account payments are all handled explicitly; you decide during scoping which of them the portal is allowed to accept.

Multi-entity, multi-currency

The portal is legal-entity aware. A customer trading with three of your legal entities sees a company selector, and each company's transactions are read and settled in that company's context with its own number sequences and posting profiles. Currency is taken from the transaction, and any realised exchange gain or loss on settlement is posted through your existing configuration rather than being calculated in the portal.

Notification and dunning support

An optional batch job issues statement and reminder emails on a schedule you define, each with a deep link into the portal. Where you already run collections letters in F&O, the portal link is added to those documents rather than replacing them.

Who this is for

Organisations running F&O with a meaningful volume of B2B invoices and a customer base that expects self-service — distributors, manufacturers selling to trade accounts, service businesses billing monthly, and any group where a shared AR mailbox has quietly become a full-time job. It is worth most where DSO is a board-level number and where the AR team is small relative to the invoice count.

It is worth least where you invoice a handful of customers on negotiated terms, or where payment is already collected by direct debit at source.

How delivery works

1. Scoping call. We walk your AR process, your posting profiles, your aging definition, your legal entity structure, your payment provider and your identity requirements for portal users. We look at your actual environment, not a generic questionnaire. 2. Fixed quote and specification. You receive a written functional and technical specification and a fixed price. The listed price is the starting point for a standard scope; anything beyond it is priced explicitly before work begins, and you approve before we start. 3. Build. Development happens in our environment against your version and your configuration. Typical lead time is one working week depending on scope and payment provider. 4. Install in test. We hand over the deployable package and deploy it into your sandbox through your LCS pipeline. You run your own UAT against your own data. We fix what UAT finds. 5. Production. Once you sign off, the same package is promoted to production through your normal release process. We are on the call for the deployment and for the first live settlement run. 6. Support. A defect support window follows go-live. Enhancements after that are quoted separately.

What we will tell you honestly

This is custom software built for your environment. It does not exist until you commission it, there is no trial version to download, and there is no instant install. If your requirement is genuinely met by a standard F&O capability you already own, we will say so during scoping rather than build around it.