Discrepancies between a carrier or MGA commission statement and the transactions in Momentum AMS can occur for a variety of reasons — such as missing policy records, mismatched policy numbers, incorrect amounts, or timing differences.
Addressing these issues promptly ensures accurate financial reporting, prevents underpayment or overpayment, and keeps reconciliation smooth.
This article explains the most common causes of commission statement discrepancies and the steps to investigate and resolve them.
Steps
Step 1: Identify the Discrepancy
Compare the carrier/MGA commission statement with the corresponding transactions in Momentum AMS.
Note any of the following:
Transactions missing from Momentum AMS.
Incorrect commission or premium amounts.
Duplicate transactions.
Policies listed in the statement that do not exist in the system.
Step 2: Verify Policy Details
Search for the policy in Momentum AMS using the policy number.
Confirm that:
The policy exists in the system.
The policy number format matches exactly with the carrier statement.
The endorsement term matches the statement’s date range.
Step 3: Check Transaction Generation
If a transaction is missing:
Go to the policy’s endorsements tab.
Verify that a transaction was generated for that endorsement.
If not, click Generate Transaction to create the missing payable and receivable records.
For detailed guidance, see Troubleshooting Missing Commission Transactions in Momentum AMS.
Step 4: Review Commission Rules
For agent commissions, confirm that the correct commission rules are set up and active.
If rules were missing or incorrect during reconciliation, update them and, if necessary, re-run the Generate Agent Commissions process.
See Troubleshooting Missing Agent Commissions in Momentum AMS for details.
Step 5: Investigate Amount Mismatches
Confirm the commission rate in the policy matches the agreed rate with the carrier/MGA.
Check for endorsements or mid-term changes that may have affected premium and commission amounts.
If the carrier statement is incorrect, contact the carrier/MGA for clarification or an adjusted statement.
Step 6: Handle Duplicate Transactions
If duplicates exist, determine if they came from:
A CSV import that was run twice.
An Ignore Duplicates checkbox setting that was incorrectly applied.
Remove or adjust duplicate transactions as needed.
Step 7: Unreconcile if Necessary
If the discrepancies are too extensive to fix within the current reconciliation:
Go to Miscellaneous → Accounting Items → Agency Statements (or Agent Statements for producer commissions).
Locate the statement in question.
Click Actions to the left of the statement.
Select Delete and choose one of the following options:
Delete just statement (leave commission payments) — Removes the statement record but keeps all commission payment transactions in place.
Delete Statement and Commission Payments — Removes both the statement and the commission payment transactions.
Delete statement, commission, and commission payments (Only use for CSV import) — Completely removes the statement, commission records, and commission payment transactions. This should only be used if the statement was imported via CSV and needs a full reset.
This process unreconciles the statement and allows you to start fresh with accurate data.
Step 8: Finalize Reconciliation
Once discrepancies are corrected, return to the Reconciliations module.
Proceed with reconciliation following the steps in:
Best Practices
Always check policy number formatting between the carrier statement and Momentum AMS before importing or reconciling.
Investigate and resolve missing transactions before finalizing a statement.
Keep detailed notes on discrepancies for audit and follow-up purposes.
Address recurring issues with carriers/MGAs to prevent repeated mismatches.
Verify import previews carefully when uploading CSV files to prevent duplicates.
Remember you can unreconcile a statement by deleting it and choosing to remove both the statement and the commission payments.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article