Skip to main content
Question

Wrong post period when adding a bill through api

  • May 7, 2025
  • 1 reply
  • 109 views

Hello, I’m currently trying to add a bill where the post period differs from the bill date. But it seems the system keeps taking the default post period based on date in case when my user profile don’t have a default branch.
When a default branch is assigned to the user profile, it appears to work correctly only for bills associated with that same branch.
For example, if the bill is in the BRANCH1 branch and the user's default branch is also BRANCH1, the Post Period is correctly populated based on the financial period of that branch.
However, when processing bills that belong to other branches such as BRANCH2 or BRANCH3 the Post Period instead defaults based on the document date rather than following the logic of the branch-specific period.

The endpoint we've tried:

/entity/Default/22.200.001/Bill

/entity/Default/24.200.001/Bill

Request Method: @PUT

Request Body:
 

{
...
"Date": {
"value": "2025-02-11T05:00:00.000+0000"
},
"BranchID": {
"value": "BRANCH1"
},
"PostPeriod": {
"value": "032025"
},
"Type": {
"value": "Bill"
},
...
"Details": [
{
...

"Branch": {
"value": "BRANCH1"
},
...
}
]
...
}

Is there a way to have the system consistently use the financial period of the bill, regardless of the user's default branch and bill date?

1 reply

  • Freshman I
  • September 23, 2025

We are running into this same issue. Has anyone gotten any updates on it or found a resolution?