Closing the Month and Posting Results to the General Ledger

Closing the Month and Posting Results to the General Ledger

Closing a month for accounting purposes and posting the results to the general ledger system is an automated process that must be triggered by the user after the end of each month. All that is required from the user is a final review of the results and a few simple clicks. 

The steps for compleing the process are listed below with instructions and explanation. 

Complete the Previous Month's Accounting Tasks

When a user is ready to close an accounting month in MarginDriver and post the results to their general ledger system, they should navigate to Accounting > Close Month & Post to GL



The first button to the left, Complete Previous Month's Accounting Tasks, simply informs the user, or the accountant or bookkeeper, that the previous month's gross profit accounting has already been completed. Completion of the previous month's accounting is a prerequisite for moving forward with any month. A green checkmark indicates that the previous month has been completed; a red exclamation point means that the previous month still needs to be completed. 

Step #1: Close Month

This first task asks the user to close the accounting month in MarginDriver which equates to locking the current data in MarginDriver. This includes all orders and revenue, as well as product and shipping costs. Most of this data is retrieved via API from the user's sales channels and payment processors but there are instances where product and shipping costs, for example, need to be updated via a flat file upload. Thus, this step is a safety net designed to remind the user that all data in the account should be up to date before moving forward with the rest of the process. If the user is satisfied with the status of the data in the account, he or she should click Close Accounting Month to proceed. 

Step #2: Post Gross Profit Statement Journal Entries

The second step displays MarginDriver's eight automatically-prepared journal entries (JEs) which comprise the monthly Gross Profit Statement (and balance sheet entries, if any). 
  1. JE #1: Product Revenue & AR

Total product sales for the month are recorded as a debit to an AR account and a credit to the product revenue account for each respective sales channel.
  1. JE #2: Shipping Revenue & AR

Total shipping revenue for the month is recorded as a debit to an AR account and a credit to the shipping revenue account for each respective sales channel.
  1. JE#3: Product Cost of Goods Sold & Inventory

Product costs are recorded as a debit to the various product cost of goods sold (COGS) accounts with a corresponding credit to inventory.
  1. JE #4: Shipping Cost of Goods Sold & AP Shipping/Amazon AR

COGS for shipping the month's orders are debited to various shipping COGS accounts with the corresponding credit going to an accounts payable (AP) shipping account. It is expected that the user will then apply all vendor payments for such shipping costs to this same AP shipping account to offset the liability of shipping cost payable recorded in this account with this JE.
  1. JE #5: Fees & AR

All sales channel fees that can be attributed directly to invidual orders are included in this JE and recorded as a debit to Fees COGS for each sales channel. In addition, the user has the option under Settings > Fees to also allocate any indirect sales channel fees to the gross profit of individual orders and therefore also be included in this JE for Fees COGS. The corresponding credits for all fees are charged to the AR account of the respective sales channel to reduce the amount owed to the seller as these fees are paid by the sales channel and they reduce the amount owed to the user. If the user elects to have indirect fees, advertising costs or other expenses that are deducted from a marketplace payout recorded as operating expenses in their GL, they will still be included in this JE but the user should manually edit the GL account number in Settings > GL Account Settings to change it from the COGS account number to an operating expense account number. 
  1. JE#6: Balance Sheet Entries & AR

There are circumstances when balance sheet transactions are run through sales channels and adjust the amount of the payments made to the seller. This includes transasctions such as loans from Amazon to the seller, as well as related loan payments back to Amazon. MarginDriver identifies these transactions, includes them in this JE and then applies the sum to one common balance sheet account. The user will needs go into this account in the GL and allocate the entries to the appropriate balance sheet accounts. An exception are adjustments to inventory which are handled separately in JE #7.
  1. JE #7: Inventory Adjustments & AR

Amazon's FBA program takes control of a seller's inventory and assumes responsiblity for fulfilling the seller's orders. If the inventory is lost, damaged or recovered by Amazon, adjustments to the Amazon payout to the seller may be in order. MarginDriver identifies these balance sheet transactions in the Amazon Settlement Reports and includes them in this JE as a debit or credit to inventory and AR.
  1. JE #8: Sales Tax US and VAT AR

Sales tax and value-added tax (VAT) collected from the seller's customer (and included in the sales channel's payment to the seller) is the responsibility of the seller to remit to the appropriate taxing authority. This collected tax is the only sales tax and/or VAT that MarginDriver records in this JE and it is therefore recorded as a debit to the AR account to include it in the AR balance and a credit to a tax liability account. 
It is recommended that users review the Gross Profit Statement before sending it off to their general ledger.  To do so, users need to simply click on the box in the middle of Task #2 titled:   

  

The Gross Profit Statement to be transferred to the user’s general ledger system with these journal entries will then appear. After a quick review and approval, the user should click again on this same button to go back to the JEs. The user will then scroll to the bottom of the page and click on the red button titled Post to QBO (or other GL system to which MarginDriver is connected). This action will post the JEs and transfer the month’s Gross Profit Statement to the user’s GL, before proceeding automatically to the third step.

Step #3: Complete AR Reconciliation

The A/R reconciliation screen displays a table that reconciles the user’s general ledger AR account balances (included in the step #2 journal entries) with each AR account’s respective third-party balance at the end of each month. Note that only the AR accounts which MarginDriver can track through integrations are included in this table; AR accounts designated as Other Gateway AR accounts are not included.

The reconciliation relies on data retrieved via API from third parties such as Amazon, Shopify Payments, PayPal, Walmart, etc. to establish their respective amounts due to the user at the end of each month. The user’s general ledger AR balance is then adjusted to agree with the respective third party’s confirmed amount due at the end of the month for unpaid orders.

Reconciliation Differences

Typically, any monthly difference between the GL balance and the third-party balance is minor and likely due to one of the following factors:
  1. Timing: MarginDriver pulls data through APIs from various sales channels and payment processors to determine the amount due to the user for each order. The payments for these orders are pulled from the same sources to determine what has been paid and what remains unpaid at the end of each month. Sometimes the actual payment amount will differ from the original estimated amount due. In such cases, MarginDriver updates the original estimated amount due in AR Order Tracking to agree with the actual payment amounts. This adjustment is only available to orders from months that have not been closed for accounting purposes. If there are differences in orders from closed accounting months, they are considered "timing differences" and they show up in the following month's AR reconciliation. 
  2. Currency Conversion Timing: This is similar to the Timing difference discussed above but it's the result of fluctuations in currency conversion rate rather than purely the timing of the payout. Estimated amounts due for orders placed using foreign currencies are calculated using the currency conversion rate in effect on the day the orders was placed. However, more often than not, the currency conversion rate in effect at the time of the payment is different. In such cases, MarginDriver will update the original estimated amount due in AR Order Tracking to reflect the change in currency conversion rate. Again, this only applies to orders in months that have not been closed for accounting purposes. If the month has been closed, the difference is designated as a currency conversion timing difference and it shows up in the following month's AR reconciliation. 
  3. Undisclosed Deposit Adjustments: Most deposits from third parties require adjustments for various non-order-specific costs such as advertising, subscription fees, loans, etc. But there are instances where small unidentified (not itemized in the payment statement) adjustments occur which increase or decrease the deposit amount. MarginDriver runs these unidentified deposit adjustments through the the AR reconciliation difference.

AR Reconciliation Table



Unnumbered Columns: The first three columns are not numbered as they only provide information about each of the AR accounts being reconciled. 
  1. Account Transactions: The View boxes in this column can be clicked on to display all of the transactions for this AR account in the user's GL. This is designed to save the user considerable time going back and forth between the MarginDriver table and their GL software to review each AR account's activity. 
  2. GL Account Name: self-explanatory
  3. Account Identifier: GL account number
There are also seven numbered columns in the AR Reconciliation table:
  1. General Ledger Balance: The column displays the GL balance for each AR account at the end of the month. The transactions for the month that generated this balance can be viewed by clicking on the View button in the Account Transactions column.
  2. Deposit in Transit (DIT): This column displays any deposits from third parties that were issued before the end of the month but did not appear in the user's GL until the following month. For example, if Amazon dates a payment on the last day of the month, it will be applied to the AR balance for that month. However, the deposit may not hit the user's bank account or GL until the first few days of the following month.  In such cases, the calculated amount due to the seller at the end of the month will be less than the AR amount in the user's GL by the amount of this deposit in transit. Therefore, this deposit becomes a reconciling item and is automatically identified as a DIT by MarginDriver and placed in the second column. The DIT automatically reduces the GL balance to facilitate proper reconciliation with the Third Party Balance. 
  3. GL Balance Less DIT (1-2): This column displays the result of subtracting any DIT amount in column two from the GL balance in column one to arrive at a GL AR balance that has been adjusted for any deposits in transit. 
  4. Third Party Balance: The amount due from each third party at the end of the month. MarginDriver calculates this balance itself relying on financial data retrieved directly from the third parties' APIs. These month-end third party AR balances can also be viewed on the respective Payment Reconcilation & AR Tracking pages along with the list of orders supporting the calculation of the balance. 
  5. GL & Third Party Difference (4-3): This column displays the difference between column three (GL Balance Less DIT) and column four (Third Party Balance).
  6. Journal Entry Amount: This column replicates the difference between columns four and three that is also displayed in column five. But the value in column five represent the amount by which the AR account will be adjusted through a journal entry. This JE is necessary to adjust the AR balance from column three to agree with the third party amount due in column four. 
  7. GL Balance Adjusted To Equal Third Party: The last column displays the new GL AR account balance after the JE from column six has been posted. 
The Edit option in columns one, two, four and six enables the user to make manual adjustments to the amounts in these columns, if needed. However, with the entries and calculations being totally automated, the need for editing is exceedingly rare. 

In the event that the reconciling difference for an AR account is unacceptably large (~ > 1% of sales channel revenue for the month), the user should contact MarginDriver Support for assistance before completing the AR reconciliation and posting the adjusting JE to the GL in the next step.

If the results of the reconciliation are acceptable, the user should click on the red Approve button at the bottom of the page and proceed to final step.

Step #4: Post AR Reconciliation Journal Entry

The journal entry in this step is the adjustment amount needed to reconcile each GL AR account to the Third Party Balance. The JE is either a debit or a credit to the AR account along with a corresponding debit or credit posted to the Fees account. Upon posting the reconciling JE to the GL, the same amount will be equally allocated across the fees for all orders for the month in each sales channel or payment gateway. 

Typically, the reconciling difference for each order only amounts to a few cents per order and it can be found in the fees for each order as AR Rec Adjustment.  This ensures that the accumulation of all of the unpaid orders in MarginDriver’s AR Accounts at the end of the month agrees with both the GL AR account balance and the confirmed Third Party AR amount due to the user. 

To post the journal entry in this step, simply click on the red Post to QBO (or applicable GL system) button at the bottom of the page. After doing so, the JE will be posted in the GL and the next month’s Close Month and Post to GL feature will appear on the screen. The user can then move on to the next month's accounting provided that month is complete and sufficient time has been allowed to capture all deposits. 

Restart Month and Reverse Journal Entries

Circumstances may arise that necessitate reversing the journal entries and restarting the accounting tasks for the month. This can be initiated by simply clicking the red button at the top right of the screen titled Restart Month & Reverse Journal Entries. Clicking this button will erase the journal entries from the GL and restart the month's accounting tasks from scratch. The month's data (product costs, shipping costs, estimated fee settings, etc.) will then be open for editing, if necessary, and the accounting tasks can be started anew.

    Article Categories