Integrations and source ownership

• Payment provider or bank. Set up the chosen source of receipt confirmation. Map its reference and amount to the intended order, and agree how Finance Officer handles delayed confirmation or a returned payment. The connection requires the provider’s access and a tested mapping.
• Accounting system. Agree how reviewed charges, voids and receipts reach the bakery’s accounting records. Decide whether an order item and a counter sale represent the same obligation before exporting totals. Reconcile accepted entries with the accounting result.
• Recipe and stock tools. If the bakery already uses a separate production system, agree which customer order reference it should receive and who maintains the information on either side. Treat that exchange as a connection to configure with the team responsible for the source.

Give each connection a named owner and a clear source of truth. Agree record matching, retry handling and what counts as a confirmed result before enabling routine transfers. Keep credentials in the approved secret store and limit access to the work the connection performs.

Rehearse a delayed payment result and a repeated source event. Finance Officer should be able to identify the affected order and explain why the local receipt is Pending or Confirmed. A successful local order action cannot stand in for the provider’s payment acknowledgment.

For accounting, use an example with a posted charge, a void and a separately confirmed receipt. Reconcile the source entries to the destination before accepting the connection. Provider access, configuration and acceptance testing determine when the connection is ready to use.

Plan the implementation with the owners of the external systems.