FE NXT SKY API Period Summary Returning Both Activity Row and Rolled Balance Row

Ty Walters

I’m seeing unexpected duplicate/extra rows from the Financial Edge NXT SKY API Period Summary endpoint, and the issue appears to be that the same credit is being represented two different ways.

For one account, there is only one transaction for the entire fiscal year. The API is returning four rows for the same fiscal year, fiscal period, and account number.

Details:

• Fiscal year: 2024-2025
• Fiscal period: 13
• Account number: 16-159400
• Period start date: 2025-06-30T00:00:00
• Period end date: 2025-06-30T00:00:00
• The transaction date is also 2025-06-30T00:00:00
• Only one transaction exists on this account for the year
• One transaction code appears: Construction / PT_MISC

The two no-transaction-code rows look like this:

Row 1:

• beginning_balance: -730437
• credit: 89167

Row 2:

• beginning_balance: -819604
• credit: 0

These appear to represent the same activity two different ways, because:

-730437 - 89167 = -819604

So one row appears to show the beginning balance with the credit listed separately, while the other row appears to show the beginning balance after the credit has already been applied.

The transaction-code rows are also returned twice with identical values:

• transaction code: Construction / PT_MISC
• beginning_balance: 2038381
• debit: 0
• credit: 0

My question is: is this expected behavior for Period Summary when the transaction date is exactly the same as the fiscal period start/end date, especially for Period 13? Or is this possibly stale/generated summary data where the same period was summarized more than once?

I’m trying to determine the correct way to consume this endpoint without double-counting balances or activity.

Ty Walters

Removed because after summarizing again, the problem reappeared.

I wanted to add one more detail. After waiting/rechecking the same Period Summary request, the extra rows disappeared.

The first response returned 4 rows for the same fiscal year, period, and account. It included what looked like both:

• a row with the credit listed separately, and
• another row where that credit appeared to already be applied to the beginning balance.

It also returned the same Construction / PT_MISC transaction-code row twice.

Later, running the same request returned only the expected 2 rows:

• one row with no transaction code
• one row with the Construction / PT_MISC transaction code

I’m not saying I can prove the first response was stale from a specific timestamp field, because the Period Summary response does not appear to include a “last summarized” or “version” value. But since the same request later returned the expected result, and the duplicate/rolled-forward-looking rows disappeared, it seems like the first response may have been a temporary or stale summary state after the summary process was rerun.

Is this expected behavior after running the Period Summary process? Should API consumers wait a certain amount of time after summarizing before pulling Period Summary data, or is there a way to confirm the summary process is fully settled before reading from the endpoint?