Dynamics Accounting: Intercompany Transfers Due To / Due From

Created by Kevin Schmidt - HCPro, Modified on Thu, 9 Oct at 3:21 AM by Kevin Schmidt - HCPro

The main benefit of Intercompany setup from CRM standpoint and maintenance is that AHIMA products will not be needed when you process payments to the AHIMA Foundation accounting company.  

 

  1. Choose Accounting 

  1. Choose Due To Due From’s 

A picture containing text 
Description automatically generated 

Depending on which way money can flow determines what you enter. A one-way transaction (only AHIMA to AHIMA Foundation) will require 2 rows 

  1. AHIMA to AHIMA Foundation 

  1. Parent Company – AHIMA 

  1. Due Type – Due to 

  1. Due to/from Company  AHIMA Foundation 

  1. GL Account – 200-2310 

  1. This account should be what matches in GP to transfer money 

  1. Choose Save and Close 

  1. AHIMA Foundation from AHIMA 

  1. Accounting Company – AHIMA Foundation  

  1. Due Type – Due From 

  1. Due to/from Company – AHIMA 

  1. GL Account  

  1. This should be the receiving account, the actual income account on the product will be used, this is the money “transfer” account.  In this situation that account is 200-2820. 

  1. Choose Save and Close  

  1. Set up the AHMA Foundation to AHIMA if needed.  I don’t believe you will need this. 

 

 

 

 

 

AHIMA to AHIMA Foundation 

Graphical user interface, text, application, email, Teams 
Description automatically generated 

 

 

The above would transfer to 

 

AHIMA Foundation from AHIMA 

Graphical user interface, text, application, email, Teams 
Description automatically generated 

 

Additional AMS Settings 

 

The following setup is only if we have two accounting companies but only one of them has an active payment processor. 

 

The following is performed through the AMS Preferences under AMS Settings. 
Table 
Description automatically generated with medium confidence 

  1. AMS preference - Altai.Accounting.CreateDueToDueFrom should be set to “true” 

  1. Altai.MultiMerchant – this should be false (so we charge the single merchant and not the individual merchants based on the company product being used).   

  1. Altai.Payment.UseAccountingCompany = false 

  1. Altai.Payments.ProcessorType: this would be PayflowPro if PayPal is being used.  Please keep in mind that the value “PlayflowPro” is case-sensitive. 

 

When you do this, it doesn’t pull credentials from the accounting company, it pulls them from the AMS preferences so: 

  • Altai.Payments.PayPalVendor 

  • Altai.Payments.PayPalUserName 

  • Altai.Payments.PayPalPassword 

  • Altai.Payments.PayPalPartner 

 

Donation Fund Setup 

 

It’s also important to ensure the Donation fund is set up correctly with the correct product.  In the scenario where we only have one active credit card processor for an accounting company, we need to ensure the product being used is associated with the correct product.  Since we want all funds collected for the foundation to be transferred to the AHIMA Foundation accounting company, we need to ensure that the product being used is set to the AHIMA Foundation accounting company.  Below are the settings that the product associated that should be associated with the “General Research Fund”. 

 
Graphical user interface, text, application, email, Teams 
Description automatically generated 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article