Select a step to inspect its data. Use zoom or Fit to explore the canvas.
PT-X is Bottomline’s payment platform. Here, it supports the UK Direct Debit journey for collecting donations with the donor’s permission.
What is PT-X, and how does it work?
Direct Debit mandate
The donor’s authorisation to collect from their bank account. It gives permission; a separate collection request moves the payment.
Bacs
The UK payment system used for Direct Debit collections. PT-X supports submission and management of payments through UK payment networks.
SharePoint
The file handoff used by this integration. Business Central stages its outbound file here; provider pickup and processing are separate stages.
How this workflow runs
Business Central keeps the donor, pledge and mandate records, then prepares registration instructions.
For a due donation, a separate collection batch contains the amount, reference and execution date.
The integration validates and archives the outbound file, then stages it on SharePoint for the intended provider handoff.
Return reports come back into Business Central: AUDDIS reports mandate outcomes, ARUDD reports unpaid collections, and ADDACS/DDIC handle supported mandate changes or cancellations.
Staff review exceptions and reconcile the payment and accounting evidence. A staged file alone does not establish bank settlement.
Example: a donor pledges £40 monthly. Registering their mandate gives permission. Each due £40 collection still needs its own payment request and recorded outcome.
CRM records the agreement’s payment method and provider. BC shows three routes: bank account → PT-X; card → Stripe; card → Paysafe. Provider selection is not a charge request. Card results feed a proposed incoming import. Posting, the Donation Ledger and CRM transaction mapping are distinct steps. Azure intake and outbound CRM synchronization follow the supplied diagram and remain unverified. Gift Aid is separate.
Bank account → PT-XSeparate tax-reclaim route → Gift Aid / HMRCReturn reports and CRM transaction sync are separate paths.Intake → Azure / CRM → Dataverse → BC
Scroll to explore · select a node
Illustrative data flow
Select a node or play the donor journey to see sample data.
Dashed connectors mark diagram-based or unconfirmed integration paths. Illustrative data. Azure intake and CRM transaction synchronization are diagram-based, not verified delivery. Card-payment connectors are proposed; BC posting does not prove settlement.