web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Project Accounting sep...
Microsoft Dynamics GP (Archived)

Project Accounting separating returns and invoices in cycle biller

(0) ShareShare
ReportReport
Posted on by Linda Brock 18

Hi,

My client has this Project Accounting question.

********************

Situation:  On occasion, Phoenix will run the cycle biller and we will have a credit transaction that combines with a new charge, creating only one transaction.

 

Example:  A return on the project for $3,000 and a new invoice for $1,400.  The cycle biller will result in an unapplied credit on the client for $,1600.  The $1,400 invoice does not exist.

 

 Our question:    Is there a way to set up a separate cycle biller that only bills the Returns?  We could run this at the end of the day and run the daily cycle biller each morning.  This would create a separate transaction for the Return and the Invoice.

 

We would be open to any other suggestions….we have such a large volume of transactions, I don’t think the manual approach is feasible.

 

*******************

Thanks,

Linda

 

*This post is locked for comments

I have the same question (0)
  • Linda Brock Profile Picture
    Linda Brock 18 on at

    Hi,

    Does anyone have any thoughts on this?

    Thanks

  • Linda Brock Profile Picture
    Linda Brock 18 on at

    anyone?

  • Verified answer
    Isaac Olson Profile Picture
    Isaac Olson on at

    Hi Linda, 

    Our Cycle Billing Maintenance window would have options for transactions types such as Timesheets, Equipment Logs, Misc Logs, Purchase Material... etc, but a Return would not be of those options as we are returning against a budget type on that list.  (Project>>Cards>>Billing Cycle)

    You could potentially run the Cycle Billings in the morning, then tell users that if they have any returns key them right away.  Then run cycle biller again so that it will only process the returns.  Another option would be to have the user manually bill returns right after they post them.  Basically make the billing part of your return process.  Enter the return, go to (Project>>Transactions>>Billing Entry) and mark it to bill on its own.  That would be one way to kind of separate those out. 

    The last thing that I can think of would be to create a SmartList for unbilled returns, so that the user knows when there is one to not include it and bill it separate or unmark it.  This way is manual but the user would know that they don't need to worry about checking unless the return shows up on the list.

    I hope this helps, and if there are any other ideas from the community who have customers in a similar situation, please feel free to chime in. 

    You could enter this as a product suggestion as well. 

    https://ideas.dynamics.com/ideas/

    Thanks!

    Isaac Olson 

    Microsoft Support

  • Linda Brock Profile Picture
    Linda Brock 18 on at

    Thanks Isaac.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans