Event Level Adjustment With Tax - Discrepancy Between Tax Amount and Tax_Jurisdictions (Doc ID 2868221.1)

Last updated on APRIL 04, 2024

Applies to:

Symptoms

When an adjustment is posted with tax on a usage event, the tax component adjusted is not as expected.

Scenario looks like this:
1. Customer created with BDOM as 1 and purchased a monthly cycle product.
2. Processed CDR which is taxable. Pipeline associated usage event with taxcode (Intrastate Usage_PTT)
3. Move PVT to next month and run billing on BDOM.
4. Billing and Revenue Manger (BRM) connects to vertex for taxation and generates bill.
5. Call PCM_OP_AR_EVENT_ADJUSTMENT to apply event level credit adjustment with tax of $2.
6. As a result, adjustment/tax_event is generated to adjust equivalent tax amount of $0.05. But tax jurisdiction has multiple entries and sum of amount is not matching with total amount on event_bal_impacts_t.
 

By looking to the CM log files, it can be seen that all the PIN_FLD_TAX_JURISDICTIONS entries are all returned, but somehow the PIN_FLD_AMOUNT is computed wrong.
Here is a snippet from ptt_usage_event_adj_cm.pinlog:
+++
D Sun Mar 27 01:32:57 2022  <HOSTNAME>  cm:25826  fm_act_usage.c:314 2:<HOSTNAME>:testnap:25823:-147790080:141:1646720881:3:root.0.0.0.1:::
     op_act_usage input flist
 # number of field entries allocated 20, used 2
 0 PIN_FLD_POID           POID [0] 0.0.0.1 /account 28457846 0
 0 PIN_FLD_EVENT        SUBSTRUCT [0] allocated 41, used 24
 1     PIN_FLD_POID           POID [0] 0.0.0.1 /event/billing/adjustment/tax_event -1 0
 1     PIN_FLD_NAME            STR [0] "Tax Event Adjustment"
 1     PIN_FLD_USERID         POID [0] 0.0.0.1 /service/pcm_client 1 91
 1     PIN_FLD_SESSION_OBJ    POID [0] 0.0.0.1 /event/billing/cycle/tax 335606133197790196 1
 ...
 1     PIN_FLD_TAX_JURISDICTIONS  ARRAY [0] allocated 20, used 8
 2         PIN_FLD_ELEMENT_ID      INT [0] 3
 2         PIN_FLD_NAME            STR [0] "Intrastate Usage_PTT|UNITED STATES|0|4|101|Universal Service Fund Surcharge|Universal Service Fund Surcharge|CA|Forest Ranch|COUNTRY|50070000|TAXABLE"
 2         PIN_FLD_PERCENT      DECIMAL [0] 0.0051
 2         PIN_FLD_TYPE           ENUM [0] 0
 2         PIN_FLD_AMOUNT       DECIMAL [0] 0.18
 2         PIN_FLD_AMOUNT_GROSS DECIMAL [0] 36.8
 2         PIN_FLD_AMOUNT_EXEMPT DECIMAL [0] 0
 2         PIN_FLD_AMOUNT_TAXED DECIMAL [0] 36.8
 1     PIN_FLD_TAX_JURISDICTIONS  ARRAY [1] allocated 20, used 8
 2         PIN_FLD_AMOUNT       DECIMAL [0] 0.03
 2         PIN_FLD_AMOUNT_EXEMPT DECIMAL [0] 0
 2         PIN_FLD_AMOUNT_GROSS DECIMAL [0] 2.000000000000000
 2         PIN_FLD_AMOUNT_TAXED DECIMAL [0] 2.000000000000000
 2         PIN_FLD_ELEMENT_ID      INT [0] 0
 2         PIN_FLD_NAME            STR [0] "Intrastate Usage_PTT|BUTTE|0|1|1|Local Sales and Use Tax|General Sales and Use Tax|CA|Forest Ranch|COUNTY|50070000|TAXABLE"
 2         PIN_FLD_PERCENT      DECIMAL [0] 0.0125
 2         PIN_FLD_TYPE           ENUM [0] 2
 1     PIN_FLD_TOTAL         ARRAY [840] allocated 20, used 1
 2         PIN_FLD_AMOUNT       DECIMAL [0] 0.03                                          !!!!!!!!!!!!!!!!!
 1     PIN_FLD_BAL_IMPACTS   ARRAY [0] allocated 22, used 22
 2         PIN_FLD_ACCOUNT_OBJ    POID [0] 0.0.0.1 /account 28457846 20
 2         PIN_FLD_AMOUNT       DECIMAL [0] 0.03                                          !!!!!!!!!!!!!!!!!
+++

As a result, PIN_FLD_TOTAL|PIN_FLD_AMOUNT = 0.03, while on PIN_FLD_TAX_JURISDICTIONS we have: 0.18 & 0.03 and so the customer's expectation would be to have the total_amount = 0.18 + 0.03 = 0.21.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.