Payment Proposal Tech Overview

1. Payment Proposal Tech Overview • A look into the payment proposal process

2. Major parts • The payment proposal process consists of four major parts: • A search for open transactions to include. • An organizer, combining transactions to be paid into actual payments. • A tool for transferring the suggested payments into a payment journal. • The payment journal itself.

3. Search (CustVendCreatePaymJournal) • Searches open transactions to be paid. • Date criteria can be Due Date and/or Cash Discount Date. • The dialog from search holds parameters used by the payment propsal organizer, e.g. ”Amount limit”.

4. Organizer (CustVendPaymProposal) • Combines transactions for payment into summarized payments • Controls features like ”Amount total”, ”Transaction total” and ”Delete negative payments”

5. Transfer (CustVendPaymProposalTransferToJournal) • Creates or updates journal lines based on the suggested payments from the proposal. • Updated is only applicable if the payment proposal is generated based on existing journal lines.

6. Helper classes • Payment date calculationAdjusts a due date or cash discount date into a payment date according to the settings for the payment proposal. A setting could for example be payment on a specific day of the week. • The CustVendPaymProposalOrg classes controlling how transactions are inserted into the payment proposal. • Payment proposal form logic handlerOne class handling the logic for both the AR and AP payment proposal.

7. Payment date calculation (CustVendPaymProposalCalcPaym) • Calculates the payment date for open transactions. • Calcualtion is based on the actual due date and/or cash discount date and then adjusted according to the parameters setup on Methods of Payment and on the Generate Payment Proposal parameters.

8. CustVendPaymProposalOrg • The payment proposal has two different models for adding open transactions to the proposal. • Transactions are added based on the search in open transactions. • Transactions are based on existing payment journal lines. • The CustVendPaymPropsalOrg classes deal with the differences between the two models. An example is that if loading from an existing journal we will match the suggested payments with the existing journal lines to be able to update the journal lines during the transfer.

9. Payment proposal form logic (CustVendPaymProposalEditForm) • The payment proposal forms (AR and AP) contain a lot of logic, for example the ability to switch the ”Linked” view on and off. • The logic is pulled out in this class to: • Keep code out the forms. • Have one code base for both AR and AP.

10. The big picture Search(CustVendCreatePaymJournal) Calculate Payment Date(CustVendPaymProposalCalcPaym) Organize(CustVendPaymProposal) Transfer to journal(CustVendPaymProposalTransferToJournal) Org. Helper Class(CustVendPaymProposalOrg) Payment Journal Form Form logic(CustVendPaymProposalEditForm) Edit Proposal Form Loading an existing journal into the payment proposal

11. Assumptions • The payment proposal is always used in the context of a payment journal. • There can be only one active payment proposal per journal.

12. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.