Dynamics GP Billing Cycle Error: Transactions Missing? Troubleshooting Tips Inside

Table of Contents

One of the common frustrations encountered when using the Project Accounting module in Microsoft Dynamics GP is discovering that expected transactions are missing from the billing cycle run. This issue directly impacts the ability to generate accurate and timely invoices for project work, potentially delaying revenue collection and disrupting cash flow. While several factors can contribute to transactions not being picked up by the Cycle Biller, a frequent cause stems from inconsistencies in how billing cycles are assigned within the system. Understanding the logic Dynamics GP uses to match transactions to a specific billing run is crucial for diagnosing and resolving this problem efficiently.

The core of this specific issue lies in the configuration of the Cycle Biller itself, specifically the “One Invoice Per” setting. This setting dictates how Dynamics GP groups transactions for invoicing and, importantly, which locations it checks for the assigned billing cycle when determining if a transaction should be included in the current billing run. A mismatch between the billing cycle assigned to a project transaction and the required cycle based on the “One Invoice Per” setting is a primary reason why transactions might be overlooked by the Cycle Biller. Identifying this mismatch is the first step in bringing those elusive transactions back into the billing process.

Understanding the “One Invoice Per” Setting¶

The “One Invoice Per” setting in the Dynamics GP Cycle Biller window (Transactions > Project > Billing > Cycle Biller) is a fundamental control that determines the granularity of your project invoices. It essentially tells the system how to consolidate billable costs and revenues. The three available options – Customer, Contract, and Project – define the criteria for creating a single invoice document. This setting also influences where Dynamics GP expects to find the primary billing cycle assignment that must match the cycle being run in the Cycle Biller window.

Choosing Customer for “One Invoice Per” signifies that all billable transactions for a single customer, potentially across multiple contracts and projects, will be consolidated onto one invoice. When this option is selected, Dynamics GP performs a critical check: it compares the billing cycle assigned on the Customer card with the billing cycle assigned on the Project card. For a transaction linked to a specific project under that customer to be included in the Cycle Biller run, the billing cycle assigned at the Customer level (Cards > Sales > Customer > Project) must match the billing cycle assigned at the Project level (Cards > Project > Project > Billing Settings). If these two assignments do not align, any transactions associated with that project will be skipped during the billing run for that cycle.

When the Contract option is selected for “One Invoice Per”, Dynamics GP is instructed to create a single invoice for all billable transactions belonging to a specific contract, which might span multiple projects under that contract. In this configuration, the system shifts its focus to comparing the billing cycle assigned at the Contract level with the assignment at the Project level. Specifically, Dynamics GP will compare the billing cycle found on the Contract card (Cards > Project > Contract > Contract Settings) against the billing cycle assigned on the Project card (Cards > Project > Project > Billing Settings). Just like the Customer setting, a discrepancy here means that transactions tied to that project will not be picked up by the Cycle Biller if the contract’s billing cycle doesn’t match the project’s cycle for the cycle being run.

Finally, if you choose Project for the “One Invoice Per” setting, you are telling Dynamics GP to generate a separate invoice for each individual project. This is the most straightforward setting in terms of billing cycle checks. When “Project” is selected, Dynamics GP only needs to look at one place for the billing cycle assignment: the Project card itself. The billing cycle assigned on the Project card (Cards > Project > Project > Billing Settings) is the sole determinant for whether a transaction associated with that project is included in a Cycle Biller run for that specific cycle. There is no comparison needed with Customer or Contract level assignments, simplifying the setup and reducing potential mismatch points related to the billing cycle.

The critical takeaway is that regardless of which “One Invoice Per” option you choose, Dynamics GP requires a specific billing cycle or set of billing cycles to be assigned in the relevant locations. If the Cycle Biller is run for a particular billing cycle (e.g., “MONTHLY”), and the project (and potentially its associated customer or contract, depending on the setting) is not assigned “MONTHLY” in the required comparison location(s), then none of the transactions under that project will be selected for billing in that “MONTHLY” run. This is the fundamental mechanism by which billing cycle mismatches cause transactions to go missing from your intended invoices.

Troubleshooting Missing Transactions Due to Billing Cycle Mismatch¶

When you encounter the situation where expected transactions are not appearing in your Cycle Biller output, and you suspect it might be related to the billing cycle assignment, follow these systematic troubleshooting steps to identify and resolve the issue. This process involves verifying the settings in the Cycle Biller window and then checking the relevant card windows based on those settings.

Step 1: Identify Missing Transactions and Associated Projects¶

Begin by identifying the specific transactions that you expected to be included in the billing run but were not. Note down the project numbers associated with these transactions. This will narrow down your investigation to the specific projects that are experiencing the issue. You can often identify missing transactions by comparing a report of billable transactions (like the Project Transaction list filtered for billable transactions) against the output generated by the Cycle Biller.

Step 2: Check the Cycle Biller Settings¶

Open the Cycle Biller window in Microsoft Dynamics GP by navigating to Transactions > Project > Billing > Cycle Biller. Pay close attention to the following settings:
* Billing Cycle: Verify that you are running the Cycle Biller for the correct billing cycle that you expect the projects/transactions to be assigned to.
* One Invoice Per: Note the selection made here (Customer, Contract, or Project). This is the crucial setting that dictates where Dynamics GP looks for the billing cycle assignment match.

Step 3: Verify Billing Cycle Assignments Based on “One Invoice Per” Setting¶

Based on the “One Invoice Per” setting identified in Step 2, navigate to the relevant card window(s) for the projects you identified in Step 1 and check the assigned billing cycles.

• If “One Invoice Per” is set to Customer:

  • Go to the Customer Card: Cards > Sales > Customer. Select the customer associated with the project(s). Click the “Project” button. On the Customer Project Options window, check the billing cycle assigned.
  • Go to the Project Card: Cards > Project > Project. Select the project(s). Go to the “Billing Settings” tab. Check the billing cycle assigned here.
  • Comparison: The billing cycle on the Customer Project Options window must match the billing cycle on the Project Billing Settings tab for the transactions to be picked up when running the Cycle Biller for that cycle with “One Invoice Per: Customer”.

• If “One Invoice Per” is set to Contract:

  • Go to the Contract Card: Cards > Project > Contract. Select the contract associated with the project(s). Click the “Contract Settings” button. Check the billing cycle assigned.
  • Go to the Project Card: Cards > Project > Project. Select the project(s). Go to the “Billing Settings” tab. Check the billing cycle assigned here.
  • Comparison: The billing cycle on the Contract Settings window must match the billing cycle on the Project Billing Settings tab for the transactions to be picked up when running the Cycle Biller for that cycle with “One Invoice Per: Contract”.

• If “One Invoice Per” is set to Project:

  • Go to the Project Card: Cards > Project > Project. Select the project(s). Go to the “Billing Settings” tab. Check the billing cycle assigned here.
  • Comparison: The billing cycle on the Project Billing Settings tab is the only place Dynamics GP checks for the cycle when “One Invoice Per: Project” is selected. Ensure this cycle matches the one you are running in the Cycle Biller.

Step 4: Resolve the Mismatch¶

If you find a mismatch in Step 3, you have two primary ways to resolve the issue:

• Option A: Correct the Billing Cycle Assignment: If the mismatch is unintentional (e.g., someone forgot to assign the correct cycle on one of the cards), update the billing cycle in the incorrect location to match the intended cycle. For example, if “One Invoice Per” is Customer, and the Customer card is set to “MONTHLY” but the Project card is “QUARTERLY”, and the intention was “MONTHLY” for billing, change the Project card’s billing cycle to “MONTHLY”. After making the correction, save the changes and attempt to run the Cycle Biller again.
• Option B: Run the Cycle Biller for the Correct Cycle: If the billing cycle assignments are correct based on your business rules, but they simply don’t match the cycle you intended to run, then the solution is to run the Cycle Biller for the cycle that is assigned to the projects/customers/contracts. For example, if “One Invoice Per” is Contract, and the Contract is “QUARTERLY” while the Project is “QUARTERLY”, but you were trying to run the Cycle Biller for “MONTHLY”, you need to change the Cycle Biller selection to “QUARTERLY” to pick up those transactions.

Step 5: Re-run the Cycle Biller¶

After correcting any billing cycle assignments or confirming you are running the Cycle Biller for the correctly assigned cycle, re-run the Cycle Biller process. Check the output to confirm that the previously missing transactions are now included.

Step 6: Consider Other Potential Causes (If Mismatch Isn’t Found)¶

If you check the billing cycle assignments based on the “One Invoice Per” setting and find no mismatches, but transactions are still missing, the issue lies elsewhere. Other common reasons for transactions not being picked up by the Cycle Biller include:

• Transaction Status: Only transactions with a billing status of “Billable” or “Ready to Bill” are eligible. Check the transaction status on the Project Transaction Entry window or a relevant report.
• Transaction Date: Ensure the transaction date falls within any date ranges specified in the Cycle Biller window.
• Billing Type: The transaction’s billing type (e.g., Time and Materials, Fixed Price, Cost Plus) must align with how billing is configured for the project/contract and the transaction itself.
• Invoice Holds: Check if the project, contract, or customer is on invoice hold. Transactions for entities on hold will not be billed.
• Billing Frequency/Next Billing Date: On the Project or Contract cards, check the Billing Frequency and Next Billing Date. Transactions may only be eligible if they fall after the last billed date and the next billing date has arrived based on the frequency.
• Unposted Transactions: Transactions must be posted in Project Accounting to be eligible for billing.
• Intercompany or Intra-company Settings: If using these features, specific configurations related to billing might prevent transactions from being picked up on the primary company’s billing run.
• Corrupted Data: In rare cases, data corruption could prevent transactions from being selected. This would require more advanced troubleshooting, potentially involving data repair.

By systematically checking the billing cycle assignments based on the “One Invoice Per” setting first, you can resolve one of the most common causes of missing transactions in the Dynamics GP Cycle Biller. If that doesn’t fix the issue, then exploring the other potential causes listed above provides a comprehensive troubleshooting approach.

Preventing Future Issues¶

To minimize the occurrence of this billing cycle mismatch error, establish clear procedures for setting up new customers, contracts, and projects within Dynamics GP Project Accounting. Ensure that the person responsible for setup understands the impact of the “One Invoice Per” setting and the necessity of assigning consistent billing cycles across the relevant cards (Customer, Contract, Project) as dictated by that setting. Implementing a checklist for project setup that includes verifying billing cycle assignments based on the chosen invoice structure can be a valuable preventive measure.

Understanding how Dynamics GP processes information based on configuration settings like “One Invoice Per” is key to maintaining smooth and accurate billing operations. By proactively addressing potential areas of inconsistency during setup and following a structured troubleshooting approach when issues arise, you can ensure that all billable project transactions are captured in the Cycle Biller and included on customer invoices as expected.

Have you encountered this specific Dynamics GP billing cycle issue? What troubleshooting steps have worked best for you? Share your experiences and tips in the comments below!