Enterprise collection automation on the Microsoft stack
Azure AD service principal
Your IT admin registers AgentCollect as an Azure AD application and grants API permissions to Dynamics 365 Finance (OData) or Business Central (API v2.0). Token-based auth via OAuth 2.0 client credentials — no user passwords involved.
AR entity and aging mapping
Map AgentCollect to your Dynamics AR aging snapshot entity (Finance) or customerLedgerEntries (BC). Set collection triggers by aging bucket, customer group, or legal entity. Multi-company environments are fully supported.
AI agents work, Dynamics stays authoritative
AI agents contact debtors and collect payments. Collected amounts post back as Payment Journal lines in Dynamics 365 Finance, or as customerPayments in Business Central — fully reconciled, no manual entry.
What syncs between Dynamics and AgentCollect
| Direction | Data | Frequency | Dynamics Entity |
|---|---|---|---|
| D365 → AC | AR ledger entries | Every 2 hours | CustAgingSnapshot / customerLedgerEntries |
| AC → D365 | Cash receipts | Real-time | CustPaymJournal / customerPayments |
| AC → D365 | Customer account status | Real-time | CustTable custom field |
| D365 → AC | Customer master data | On sync | CustTable / customers |
| D365 → AC | Legal entity / company info | On sync | CompanyInfo (multi-company) |
Tech stack: OData REST APIAzure AD OAuth 2.0DataverseBC API v2.0Multi-company
Built for enterprise Microsoft stack teams
Native Dataverse/OData integration
AgentCollect uses Dynamics' native OData REST API — the same interface your existing Power BI reports and Power Automate flows use. No middleware, no Zapier, no custom development.
Multi-company and multi-legal entity
Full support for Dynamics multi-company environments. Configure separate collection rules per legal entity, route to different AR owners, and keep collections data scoped by company.
Azure AD security model
AgentCollect integrates as a registered Azure AD application. IT controls permissions via standard Azure RBAC. No shared passwords, full audit trail, revocable at any time from Azure Portal.
Microsoft Dynamics integration FAQ
CustAgingSnapshot and CustomerTransactions entities and write back to the CustPaymJournal entity for cash application.customerLedgerEntries and agedAccountsReceivable endpoints and post payments back as customerPayments.msdyn_collectionStatus or equivalent BC table field). This allows your AR team to see collection status directly in Dynamics without switching tools.Ready to automate your Dynamics collections?
Native OData integration. Azure AD auth. Zero custom development. Success-only fees.
Start a free pilot →