Document note only. Field Ledger is not a tax firm, cloud reseller, dental office, or insurer. Read your own form and confirm it with the preparer, billing desk, carrier, or another licensed professional.
This administrative process compiles standalone support-plan charge pages alongside official support vs compute comparison tables, for use with organizational bookkeeping workflows including the Field Ledger enterprise cloud invoice tracking system. It is intended solely for administrative organization, and does not constitute billing, tax, or financial advice; all entries should be verified with your licensed billing administrator, cloud service provider, or tax professional before formal submission. Segregating support charges from core compute line items reduces audit risk, simplifies cost center allocation, and ensures you can quickly locate supporting documentation for any support charge inquiry. This workflow applies to all enterprise cloud invoices, regardless of provider, and aligns with standard record-keeping requirements for federal tax and internal audit purposes.
Charge allocation column specifications for support vs compute table datasets
The support vs compute table is the core reference document for all charge segregation, and must include standardized columns to ensure consistency across billing periods and teams. All columns must be populated for every line item, unless marked as conditional in the specifications below. The table must be saved as a non-editable PDF and an editable CSV file for long-term storage, with version control tracking for any updates made after initial posting. Any discrepancies between the table total for SUP charges and the total listed on your official cloud invoice must be documented in a separate reconciliation log stored in the same folder as the table. Required column specifications for the table are below:
| Column ID | Column Name | Required Data Type | Support Charge Applicability | Compute Charge Applicability | Field Notes |
|---|---|---|---|---|---|
| 1 | Line Item Posting Date | ISO 8601 formatted date (YYYY-MM-DD) | Yes | Yes | Date the charge was officially posted to your organization’s cloud billing ledger, not the date the service was rendered |
| 2 | Unique Resource Identifier | 16-character alphanumeric string | Conditional | Yes | Only populated for support charges tied to a specific compute resource; leave blank for enterprise-wide support plan charges that apply to all cloud resources |
| 3 | Charge Category Code | 3-letter standardized code | Yes | Yes | Use SUP for all support-plan related charges, CMP for all core compute, storage, and network usage charges |
| 4 | Pre-Tax Charge Amount | Decimal value rounded to 2 decimal places | Yes | Yes | Full line item amount before any promotional discounts, service credits, or tax calculations are applied |
| 5 | Cost Center Allocation ID | 6-character alphanumeric string | Yes | Yes | Internal department or project ID assigned to the charge for internal cost tracking purposes |
When populating the table, sort all entries first by posting date, then by charge category code, to group all support charges together for easier reconciliation. All entries marked with the SUP category code must have a corresponding standalone support-plan charge page stored in the dedicated folder outlined in the next section.
Dedicated folder storage for standalone support-plan charge page documents
All standalone support-plan charge pages must be stored in a segregated folder structure, separate from compute charge documentation, to eliminate confusion during audit or invoice review. The top-level folder should be named for the billing period, using the format [Fiscal Year] – [Billing Period Number or Month Range], with two mandatory subfolders: Standalone Support Charge Pages and Compute Charge Documentation. Each individual support charge page file must be named using the format [Charge Category Code] – [Support Contract ID (if applicable)] – [Posting Date] – [Table Row Number], to enable quick cross-reference with the support vs compute table. Scanned copies of physical support charge invoices must be saved at 300 DPI, with no cropped edges or blurry text, and all embedded annotations (like internal approval stamps) must be fully visible in the scanned file. Do not store unrelated documents, such as support ticket logs, service upgrade requests, or vendor communications, in the Standalone Support Charge Pages subfolder; store those items in a separate Vendor Communications subfolder in the top-level billing period directory to avoid cluttering charge records. Illustrative example: A folder for the 2024 Q2 billing period would include subfolders for Standalone Support Charge Pages, Compute Charge Documentation, Vendor Communications, and Reconciliation Logs, plus the master support vs compute table saved in both CSV and PDF formats in the top-level directory. Access to the folder should be restricted to authorized billing, finance, and audit staff only, with edit permissions limited to designated billing administrators to prevent unauthorized changes to stored records.
Paper submission form requirements for verified support-plan charge records
If you are submitting physical copies of support-plan charge pages for internal audit, tax filing, or cost allocation review, you must include a standardized cover sheet for each batch of documents, plus verification markings on each individual charge page. The cover sheet must include the billing period, total number of support charge pages included in the submission, total pre-tax support charge amount matching the SUP category total from the master support vs compute table, name and employee ID of the preparer, and signature of the authorized finance lead confirming the charges are valid business expenses per organizational policy. Each individual support charge page must include a verification stamp in the bottom right corner, with fields for preparer initials, verification date, and the corresponding row number from the support vs compute table. Do not use staples on individual charge pages, as staple holes can obscure critical data like charge amounts or contract IDs; use acid-free binder clips to group pages by posting date, with a removable tab noting the date range for each group. If you are submitting records to a third-party auditor, you must also include a printed copy of the master support vs compute table, with all SUP category entries highlighted for easy cross-reference. Incomplete submissions, such as those missing a cover sheet, verification stamps, or a matching table total, will be returned for revision before processing, so cross-check all requirements before submitting.
Printed page box labeling for separate support-plan charge documentation
For long-term archival storage of printed support-plan charge pages, use standard archival-grade document boxes, with clear, standardized labeling to avoid mixing with compute charge records or other financial documents. Each box must have a weather-resistant adhesive label applied to the front face, with the following required fields: archive start date, archive end date, document type, total page count, corresponding master support vs compute table unique ID, retention period end date per your organization’s document retention policy, and packer initials. Add a 2×3 inch red sticker with the text “SUPPORT PLAN CHARGES ONLY” to the top left corner of the box, to distinguish it from compute charge boxes which use a blue “COMPUTE CHARGES ONLY” sticker. Do not write any handwritten notes on the label outside of the designated packer initials field, as unapproved annotations can lead to confusion during record retrieval or audit. Illustrative example: A box holding all 2024 support plan charge pages would have a label listing archive start date 2024-01-01, archive end date 2024-12-31, document type Support Plan Charge Pages, total page count 187, table ID SUP-CMP-2024-MASTER-V2, retention end date 2031-12-31, and packer initials JDS. Store all support charge boxes in a designated secure archival area, separate from compute charge boxes, with a log tracking box location and access history for audit purposes.
Cross-reference note placement linking charge pages to support vs compute tables
Every entry in the support vs compute table marked with the SUP category code must have a clear, traceable cross-reference to the corresponding standalone support-plan charge page, to eliminate gaps during invoice review or audit. For digital charge pages, add the corresponding table row number to the end of the file name, as outlined in the folder storage section, and include a Document Reference column in the editable CSV version of the table that lists the full file path to the corresponding charge page. For printed charge pages, write the corresponding table row number in the top right corner of each page using light blue ballpoint pen, to avoid obscuring any pre-printed data on the invoice. If a support charge applies to multiple cost centers, add a note in the Field Notes column of the table listing all cost center IDs the charge is allocated to, plus the percentage of the charge assigned to each cost center, and cross-reference the note to the internal cost allocation approval form stored in the Vendor Communications subfolder. If you make any edits to the support vs compute table after initial posting, such as correcting a charge amount or updating a cost center ID, update the cross-reference notes on all corresponding charge pages to match, and document the change in the reconciliation log for the billing period. All cross-references must be validated by a second billing administrator before the table is finalized and saved as a non-editable PDF for long-term storage.
Next action: Pull your most recent enterprise cloud billing statement, separate all support-plan charge line items onto their own labeled pages, and populate the first three columns of a new support vs compute table to align with the specifications outlined in this guide.
Filed by Field Ledger.