NOAL Registration-to-Priority Integration Platform
A dedicated integration layer connecting the organization's existing registration website to Priority — so receipts and donation receipts are recorded in the financial system through a controlled, traceable and recoverable process.
- Priority ERP
- Integrations
- Financial processes
- Production
The illustration shows the structure of the solution: Priority ERP as the financial system, the gateway and integration system built by Agile-ERP, and the organization's existing registration website.
- Sector
- National youth organization
- Status
- Running in production.
The challenge
Registration and payment take place on a public website, while the financial records are kept in Priority. Every payment on the website has to become a financial document in the financial system — without a document being created twice, and with the ability to know at any moment what happened to each action.
Why a standard implementation was not enough
A direct point-to-point connection between a website and a financial system looks simple, but it ties the website to the ERP's internal structure and leaves the critical moments unanswered: what happens when the financial system responds late, when the same request arrives twice, or when an action fails halfway. In financial processes these are not edge cases — they are the cases that decide whether the records can be trusted.
Architectural approach
The website stays focused on registration and the user experience, Priority remains the financial system of record, and a controlled layer was built between them: registration website → integration layer and gateway → Priority. Incoming requests are validated and recorded before any action reaches Priority, every financial action carries a unique business identity, and an uncertain outcome is checked against Priority before any retry. Test and production environments are separated, and moving to production is governed by an explicit policy.
What was delivered
- Creation of receipts and donation receipts in Priority from payments made on the registration website
- Validation of incoming requests before any action reaches Priority
- A unique business identity for every financial action, so a repeated submission leads back to the original result rather than creating another document
- Bounded retries, and a check against Priority when an action's outcome is uncertain — rather than blindly trying again
- Tracking of every run and each of its steps, with an audit trail
- An operations console with a dashboard, run history, a failures queue and permission-based recovery actions