Integrations and source ownership

• Banks and payment gateways. Receive challan confirmations with a provider event ID, taxpayer and amount.
• Taxpayer portal. Publish demands and receive returns or supporting documents as evidence.
• Authority assessment system. Import assessment orders with their reference, jurisdiction and amount.
• Main accounting system. Export posted journals by period.
• Identity provider. Map staff sign-in to team members; removing a leaver’s access must also remove their system access.

Each connection needs an agreed source of truth, a field mapping, a stable event identifier and a retry policy. A resent bank file must not create a second receipt, and a retried posting must not post twice. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a provider timeout, a duplicate file and a revoked credential before turning on schedules. Availability depends on each provider’s API, access agreements and configuration.

Use the implementation plan to agree acceptance criteria for each connection.