The 'Action' menu of a DSS contains the GL account Mapping Report. This report breaks down all of the payment types and sales accounts for a given day. Analyze this report first to see if mapping issues occurred.
If the GL Account Mapping is correct, go to the DSS Validation Report to see why the sales accounts and payment types did not balance.
Report Columns
Column | Description | |
|---|---|---|
1 | GL Account Name | The name of all GL accounts assigned to each type of sale |
2 | Sales Account Category | The sales category assigned from your {{glossary.POS}} after the first import |
3 | Amount | The amount of sales reported to that GL account |
4 | GL Type | The GL Type assigned to the GL account |
5 | Sales Account Type | This type tells the system how to account for each sales account. The Sales Account record assigns each GL account to a sales account |
6 | Payment Type Name | The name given to payments and discounts in your POS that the system imports into {{glossary.R365}} |
7 | Payment Group | The group assigned to each payment type in R365 |
FAQ
What should I do if the GL Account Mapping isn't correct?
Not every mismatch means a mapping is wrong — first confirm which Sales Accounts or Payment Types are out of balance. Review the Missing and Out of Balance Daily Sales Summaries article to compare the POS data against the DSS journal entry and find the exact discrepancy.
What does an incorrect or missing GL Account mapping look like on this report?
A mapping issue typically shows up as a blank GL Account Name or GL Type cell for a Payment Type or Sales Account Category that should have one assigned. Learn more about balancing journal entries to compare the Validation Report against this report to confirm which row is causing the imbalance.
For steps to correct an identified mapping issue, see Troubleshoot POS-to-GL Sales Account Mapping Errors.