Overview
Use external system connections, field mappings, object mappings, sync runs/items/cursors/conflicts, tax calculations, tax rates, and exchange-rate records.
Problem
Finance operations often need governed synchronization with accounting, ERP, tax, or rate systems.
Solution
Model each external connection and its mappings in PayStream, then use durable synchronization records and scheduled workers for finance exchange.
How it works
Configure the external system, map fields and objects, queue or execute sync work, retain run/item/cursor/conflict state, and maintain tax and exchange data alongside billing records.
Who is this for
Expected outcomes
- Auditable external finance synchronization
- Mappings and sync history retained with finance operations
Key metrics
Security impact
- External system connections, field mappings, object mappings, sync runs/items/cursors/conflicts, tax records, exchange rates, invoices, and payments · PII: yes where billing, customer, payment, bank, invoice, or external reference data identifies a person or organization
Compliance
- Workspace permissions, trusted execution, resource authorization, Core secrets, finance audit, and app-scoped grants.