Receipts

An integration receipt records the provider, external event ID, received time and payload hash alongside its processing status. The Finance Officer can inspect received, applied, rejected and failed outcomes. This gives the team a place to investigate a provider event without confusing a received message with an applied business change.

Suppose a connected system sends an event about an application subscription. The receipt identifies the provider and external event. If processing fails, the team can find the exception by provider and time. The subscription or usage record should be checked separately before anyone concludes that an allocation or commercial term changed. The receipt describes event handling; the operational record describes the current business fact.

• Source. Record the provider and external event ID for traceability.
• Integrity. Retain the payload hash and received date with the event.
• Outcome. Use received, applied, rejected or failed status to review handling.

Choose each provider connection and define which event types the team will process. Agree who investigates rejected and failed receipts and who can mark an event applied after the target record is checked. The external event ID is useful when a provider resends an event; compare it with existing receipts before treating the second delivery as new work.

The Finance Officer needs a clear way to hand a subscription or usage discrepancy to the Service Manager. A receipt may be technically received while the intended operational update still needs attention. Keep the provider event and the target record visible to their respective owners so the follow-up is based on evidence.

Record one event with a provider, external ID, received time and hash. Set its status to received, then inspect the intended subscription or usage record. Once the event has been handled, record applied. In a second case, record a failed outcome and ask the Finance Officer to locate it in the exception list.

The reviewer should be able to distinguish the two outcomes and identify the provider event to investigate. If an event ID is seen again, compare it with the prior receipt and the target record before acting. The Service Manager should confirm any resulting change in a subscription or allocation on that record rather than relying on the receipt status alone.

• Receipt exceptions — Rejected and failed provider events needing follow-up.
• Subscription renewals — Application terms to check when a provider event affects a subscription.

See subscription review and service request handling.