- Help Center
- Integrations Page
- Microsoft Dynamics 365 Business Central
-
New to Peakflo?
-
Accounts Payable
- Getting Started
- Rules
- Approval Workflow
- Custom Fields
- Vendors
- Purchase Requests
- Purchase Quotes
- Purchase Orders
- OCR
- Bill Management
- My Approvals
- Goods Receipt Notes & Service Receipt Notess
- Budget
- Reconciliation
- Reports
- Wallet & Transactions
- Payments
- Vendor Onboarding Management
- Vendor Portal
- WhatsApp Vendor Portal
- Three-way Matching
-
Accounts Receivable
-
Integrations Page
-
Travel & Expense Management
-
Payment Automation
-
Legal Notes
-
Latest Releases
-
Invoice Management
-
Reports
-
General Questions
-
Offboarding
-
Vendor Portal
-
Peakflo Ticket Portal
Why is my transaction showing a sync failure while syncing from Peakflo to Microsoft Dynamics NAV?
Cause:
This issue occurs when a transaction fails to sync from Peakflo to Microsoft Dynamics NAV with a status code 400, indicating an internal error. The error message specifies [Internal_EntityWithSameKeyExists] The record in table Gen. Journal Line already exists
, with identification fields and values matching the transaction being synced. This typically happens when attempting to create a payment for the same bill twice, leading to a duplication error.
Resolution:
Since the error is due to attempting to create a payment for the same bill twice, it's necessary to cancel the send payment creation to avoid duplication. This action prevents the duplicated payment from being created and helps maintain data integrity.
If you require further assistance or encounter any difficulties, please contact our support team for help at support@peakflo.co