Skip to main content
SarikaB96
Member
September 7, 2026
Solved

Account Rec supporting Management

  • September 7, 2026
  • 1 reply
  • 55 views

We have noticed that our application space is increasing significantly month over month. After analyzing the issue, we determined that the primary driver is the upload of supporting documentation within the Account Reconciliation module.

It is currently difficult to identify which files are consuming the most storage and the specific accounts to which they are attached. Having greater visibility into file sizes and associated accounts would help us better manage the volume of supporting documents being loaded into the system.

Additionally, could you advise on the recommended file types for attachments that provide good document quality while minimizing storage consumption? Understanding which file formats typically have the smallest file sizes would help us establish guidelines and optimize storage utilization within the application.

Best answer by Avatar-Roku

​@SarikaB96 

I recently went through something relatable. Whenever a user uploads supporting files (think it’s called S/T doc?) in the recs, they get converted to binary and stored in the recon support table.

The database name might be different on your end, but just look for  “FileBytes” column.

If you run a quick Data Adapter query, it’ll show you exactly which files are consuming up the most space. I ran it for my environment and surprised to see 200MB docs. lol

Edit: I haven’t had time to experiment but with a bit of extra SQL, you can UNION the two tables on the ReconID to pull the template and its associated account. From there, you can just filter by timestamp and user for extra granularity.

SELECT 
    FILENAME,
    CAST(ROUND(DATALENGTH(FILEBYTES) / 1048576.0, 2) AS DECIMAL(10,2)) AS [File_Size_In_MB]
FROM "Enter your recs support table name"
ORDER BY [File_Size_In_MB] DESC;

Speaking of file sizes, I looked up and it turns out saving as .XLSB cuts down the size. I tested it with the exact same content saved under both extensions. It gave me about a 25-30% reduction, which  I think is pretty significant in the grand total.
 


Lmk what you find.

1 reply

Avatar-RokuAnswer
Contributor
October 1, 2026

​@SarikaB96 

I recently went through something relatable. Whenever a user uploads supporting files (think it’s called S/T doc?) in the recs, they get converted to binary and stored in the recon support table.

The database name might be different on your end, but just look for  “FileBytes” column.

If you run a quick Data Adapter query, it’ll show you exactly which files are consuming up the most space. I ran it for my environment and surprised to see 200MB docs. lol

Edit: I haven’t had time to experiment but with a bit of extra SQL, you can UNION the two tables on the ReconID to pull the template and its associated account. From there, you can just filter by timestamp and user for extra granularity.

SELECT 
    FILENAME,
    CAST(ROUND(DATALENGTH(FILEBYTES) / 1048576.0, 2) AS DECIMAL(10,2)) AS [File_Size_In_MB]
FROM "Enter your recs support table name"
ORDER BY [File_Size_In_MB] DESC;

Speaking of file sizes, I looked up and it turns out saving as .XLSB cuts down the size. I tested it with the exact same content saved under both extensions. It gave me about a 25-30% reduction, which  I think is pretty significant in the grand total.
 


Lmk what you find.

    Terms & ConditionsAccessibility statement