The timings below describe provider capabilities. Your AMLOK refresh mode and schedule are agreed for the connection, product, and workflow. A provider’s typical interval or webhook timing is not an AMLOK delivery SLA.
How updates reach AMLOK
Provider refresh capabilities
Open an integration for its scope, requirements, and detailed refresh notes. Official provider references are linked in each row.Payments and POS
Ecommerce
Accounting
Inventory and ERP
Bank Integrations
Lender Systems
Agree the synchronization schedule
During onboarding, identify the resources needed for Insights and Signal, the available source update method, the synchronization schedule, and any allowed on-demand refreshes. Include provider entitlements, API quotas, customer consent, and any desktop or institution configuration. For event-based connections, include periodic reconciliation where the provider supports it. For scheduled bank connections, align retrieval with completed source refreshes. Additional upstream refreshes may require a provider entitlement or fee and may be restricted to specific business cases.Interpret freshness correctly
- Check the last successful source refresh and synchronization, rather than the time a request was submitted.
- Treat pending transactions, later postings, reversals, refunds, and corrections as changes that can arrive after the original record.
- Reconnection, expired consent, MFA, outages, and throttling can delay updates. A successful read of cached data does not prove that the source refreshed.
- Different resources from the same provider can have different update paths. An invoice webhook does not establish the freshness of a bank balance or financial report.