Manual Cost Entry: Manage Cloud Cost Without an API
Private cloud, IDC, niche clouds, offline or reseller statements that can’t auto-sync? Mof’s manual entry brings that cost into the same read-only table as your connected clouds: cost allocation, anomaly alerts, dashboards and Excel export.
Spreadsheets · roll your own
Excel sheets
Invoice PDFs
Reconciliations
Email threads
Manual, error-prone and slow — no allocation, no alerts, no dashboard
Mof · manual entry, full power
No API needed — still get allocation, alerts and dashboards
Why teams use Mof for manual cost entry
Some cost can’t auto-sync: private cloud / on-prem IDC, niche clouds, offline or reseller monthly statements, or parts of a hybrid setup. It used to live in spreadsheets — rolled up by hand, error-prone, and impossible to analyze alongside everything else — so “how much did we spend?” and “whose is this?” stay fuzzy.
Mof is a FinOps platform for teams running more than one cloud. Its manual entry brings that cost in without an API — entered by form or bulk import and treated exactly like an auto-synced bill: the same allocation, virtual tags, anomaly alerts and Excel export, all in one view.
Ways to track cost without an API — each with a catch
Excel ledgers, invoices, ERP entry — each records a piece, but all are hard to maintain, allocate and compare across clouds.
- Hand-typedCopy-paste row by row, easy to misalign
- Version sprawlMany edits and copies — which one is current?
- No allocation / alertsFormulas only; nobody knows when cost moves
- No cross-cloud mergeMany clouds, many sheets, merged by hand
- Totals onlyNo detail by resource / team
- Different formatsEach cloud / reseller invoice differs
- Month-end onlyLagging — anomalies found too late
- Built for accountingNo cloud trends, drill-down or allocation
- Too coarseBooked to GL accounts, no resource tags
- Two systems to keepCloud one place, finance another — never aligned
How Mof solves these
Manual data is treated the same — allocation, alerts, dashboards and export, all included.
Manual / spreadsheets vs Mof
| Dimension | Manual / spreadsheets | Mof |
|---|---|---|
| Entry method | Hand-typed in Excel | Form / bulk import, validated |
| Error rate | Formulas / copy-paste errors | Structured validation, history |
| Cross-cloud merge | Many sheets by hand | Same table as API-connected clouds |
| Cost allocation | Spreadsheet formulas, hard to split | Showback + virtual tags, by rule |
| Alerts | None | Budget / anomaly to Slack, email & IM |
| Dashboards / trends | Chart it yourself | Ready dashboards + custom views |
| Export | The spreadsheet itself | Clean one-click Excel export |
| Collaboration | Emailed around | Multi-user, role-based access |
| Real payable | Offline / reseller hard to compute | Custom discounts → real payable |
Manual cost entry FAQ
When should I use manual entry?
For cost that can’t auto-sync yet: private cloud / on-prem IDC, niche clouds Mof doesn’t support yet, offline or reseller monthly statements, or parts of a hybrid setup you track separately. Once entered, it’s managed like any auto-synced cloud.
Does manual data support allocation and alerts?
Yes. Mof treats manual data and auto-synced bills the same — the same cost allocation, virtual tags, budget / anomaly alerts, dashboards and Excel export.
Can it sit alongside my API-connected clouds?
Yes — that’s the point. Mof unifies manual cost with AWS, Alibaba Cloud, Tencent Cloud and others in one table and one schema, so trends, allocation and anomalies stay together.
Is entry tedious? Is bulk import supported?
Bulk import is supported. Beyond entering rows in a form, you can import from a template or paste a table to load a whole period at once, with field validation.
Can manual data be exported to Excel?
Yes. Mof exports manual and allocated data to clean Excel for finance to audit and book.