Lockbox Tests

From Opentaps Wiki

Jump to: navigation, search

Contents


Prerequisites

You need a fresh database installed with seed and demo data. Or, you should load the file hot-deploy/financials/data/DemoLockbox.xml


Testing Lockbox Batch Management

  1. go to /financials/control/manageLockboxBatches
  2. upload hot-deploy/financials/data/TestLockbox.mbx

Testing the First Lockbox Batch

  1. open the first batch TestLockbox030
  2. the first check has one application with error (Error - No Customer # - Bad Invoice #)
    • create an application of the remaining $900.75 to any customer
    • the check is then marked as Ready
    • the created application displays the note No Invoice #
  3. the second check should already be fully applied and marked as Ready
  4. the third check has two application lines
    • none of the two should have any applied amount since one of them has an error (Lockbox Amount Greater Than Invoice Open Amount)
    • change application to DemoLBCust/LB0003 to $500 and cash discount of $100 to completely apply the invoice
    • create an application of $500 to LB0002
    • create an application of the remaining $500 to customer DemoLBAcct
    • the check and applications are Ready
  5. the last check is applied to DemoLBCust / LB0004
    • $1250 should already be applied
    • the check is Ready and the application displays a note Partial Payment meaning that the invoice still has an outstanding amount
  6. click Process Items
  7. all checks are now applied and
    • the batch pending amount is now $0
    • there should be no more form input available
    • trying to click on Process Items results in error No line ready to process found.
    • since we fully applied all the invoices concerned except LB0004, the open amount listed in ERP Invoice Amount should be 0$ for them
  8. check invoice LB0003 for example
    • invoice items total is $600
    • payment applied is $500
    • invoice is now Paid
  9. check invoice LB0004
    • invoice items total is $1550
    • payment applied is $1250
    • invoice is still Pending
  10. go back to the Manage lockbox screen
    • TestLockbox030 should not be listed anymore

Testing the Second Lockbox Batch

  1. select the batch TestLockbox032
  2. the first check has $302.15 applied but only $300 remains for the invoice LB0004
    • set the cash discount to -$2.15
    • the check and applications are now marked Ready
  3. the third check is already marked ready
  4. click Process Items
    • the first and third checks are applied
  5. the batch pending amount is now $302.15 which is the amount of the second check
  6. check invoice LB0004
    • invoice items total is $1550
    • two payments are applied: $1250 (from the first batch) and $300 applied from a $302.15 payment
    • invoice is now Paid
  7. the second check has $302.15 but only $300 is outstanding for the invoice LB0005
    1. create a new AL line with amount of $302.15 and cash discount of -$2.15 to the invoice LB0002. Now this line should be ready.
    2. Click on [Process Items]
    3. Verify the invoice LB0005:
      • Has a status of paid
      • Has a payment of $300 applied to it and no invoice adjustment
    4. Verify the payment application has $300 applied to the invoice LB0005 and $2.15 applied to the GL Account 511000 (PROMPT PAYMENT DISCOUNTS)

Testing Lockbox File Validation

  1. go to Financials > Receivables >> Manage Lockbox Batches
  2. upload hot-deploy/financials/data/TestLockboxInvalid-bad-batch-amount.mbx
    • verify that the following error appears: Mismatch between batch total [5350.75] and actual checks total [4350.75] for batch ID [TestLockboxInvalid-bad-batch-amount030]
  3. upload hot-deploy/financials/data/TestLockboxInvalid-duplicate-application-id.mbx
    • verify that the following error appears: Check number [3012345678] has payment applications with the same sequence id.
  4. upload hot-deploy/financials/data/TestLockboxInvalid-duplicate-check-id.mbx
    • verify that the following error appears: Check ID [001] occurs in batch more than once
  5. upload hot-deploy/financials/data/TestLockboxInvalid-duplicate-check-num.mbx
    • verify that the following error appears: Check number [5012345678] occurs in batch more than once.
  6. upload hot-deploy/financials/data/TestLockboxInvalid-duplicate-batch-id.mbx
    • verify that the following error appears: Unexpected new batch, has same batch number [030] as an already parsed batch.


© Open Source Strategies, Inc. Development of this documentation site is sponsored by Open Source Strategies, Inc.
Help support opentaps with a subscription to this documentation site.