Capitalisation you can defend to an auditor.
SAP automates the two ends of a capital project. The middle, deciding what the project became, is typed by hand. Attesta decides and evidences it: amounts from a cost source, a different user approves, and SAP's own run posts.
SAP automates both ends. The middle is typed by hand.
Standard SAP carries project cost into the asset under construction. Once a settlement rule exists, SAP posts the settlement, and asset-class rules drive depreciation. Those are the two ends.
On most estates the middle stays manual: which equipment the project created, how that equipment links to fixed assets, which final assets, IAS 16 components and shares it becomes, and creating the masters. Where SAP now proposes a settlement rule with AI (S/4HANA Cloud Private Edition), the questions an auditor asks next stay open: from which cost source, by which rule, approved by whom, and did SAP post exactly that. Attesta decides and evidences that middle. Amounts always come from a cost source, a different user approves, and Attesta exports asset masters and a settlement rule. SAP's own run posts, and the evidence pack is a printable file your team attaches to the asset in SAP.
Diagnose. Align. Capitalise.
Runs standalone beside your ERP and never writes to it. It reads the as-built equipment list and the cost on the asset under construction, proposes the decision, and governs approval. Attesta never posts.
Diagnose
Load your AUC, equipment and asset extracts as CSV. It reports AUC ageing, late depreciation start and ghost assets, with the balance on each finding. Read-only. Scope is agreed in writing after the concierge.
Align
Rules carry the deterministic bulk; a transparent model that learns from your own approvals can suggest matches for messy non-SAP data, with a confidence score and a reason you can audit. Your team approves in a workbench, and the approver is a different user from the proposer.
Capitalise
Final assets, IAS 16 components and shares are split from a cost source and tie to the AUC to the cent. Attesta exports the asset masters and a settlement rule. SAP's own period-end run posts. The evidence pack is a printable file your team attaches to the asset in SAP.
Standalone first. Coupled when you're ready.
No ERP project required to start. Attesta runs on its own — CSV in, evidence out — and can couple to your systems through connectors later. Today only file exchange has been exercised.
Run it anywhere
One command or one container: persistent database, role-based sign-in, the full engine set. Load your extracts as CSV and run a first proposal in the first week, once rules and component templates exist. Your data stays a plain local file you can delete.
Exchange, don't integrate
The pattern every ERP already supports: exports in, posting documents out. Attesta reads your equipment, asset and AUC extracts and emits asset masters and a settlement rule as files your SAP team loads. SAP's own run posts.
Connect later
A connector can be attached by configuration: SAP released APIs, or your iPaaS facade. Same engines, same audit trail; a connector is transport, never judgment. None has run against a customer system yet, and the pilot uses CSV only.
any ERP, file exchange
● WORKS TODAY (files)
Integration Suite or another iPaaS
◐ WORKS ONCE POINTED AT YOUR FACADE · untested on a live system
released APIs (on-prem & cloud)
◐ WIRE-READY (reads) · not yet run on a customer system
via Cloud Connector
○ PLANNED · CSV files today
● works today · ◐ wire-ready: code exists, needs your system and credentials, has not run on a customer system; Attesta does not post · ○ planned: not yet wired. The pilot journey records zero connector writes.
"Show me the asset behind this dollar — and show me where the dollar came from." An auditor's question (illustrative, not a customer quote). Attesta answers it from a cost source, with an evidence pack your team attaches to the asset in SAP.
Sample evidence pack
The document a team attaches to the asset in SAP. Synthetic data, one decision.
Open the evidence packSame pack, machine-readable
The JSON behind it, for an auditor's tooling or your own checks.
Open the JSONTwo-minute walk-through
A screen recording of one decision from proposal to read-back, with captions.
Watch belowWhat Attesta does not do yet
Read this before you agree a pilot scope. The full list, with how each item was checked, ships with the pilot pack.
- Not yet proven on a client's S/4. The export files have not been loaded into a real SAP system. The first load at your site may need changes, so we agree a first run with your SAP team.
- Attesta never posts to SAP. It produces the asset list and the settlement rule. SAP's own run posts. Reads back by upload, not by live connection.
- Single currency. One currency and one company code per asset under construction, with no translation. A multi-currency project cannot be split correctly.
- Book depreciation only. No tax books, leases, foreign exchange, borrowing-cost computation, group assets or parallel-ledger postings.
- Data in by CSV. No live feed from your ERP. Other ERP connectors are skeletons with no live calls.
- Pilot hardening is limited. Named users with passwords, no single sign-on in the standalone edition, no independent security test or certification yet.
- One instance, one client, no high availability. A host failure means a restore from backup.
- You own the accounting outcome. Attesta is decision-support software and gives no accounting, tax, audit or legal advice.
Prove it on one completed project.
We take one real, completed project and componentise it with Attesta's engines, offline: the equipment it created, the final assets, the IAS 16 components and each share, every amount from a cost source. You get the asset masters and a settlement rule for your SAP team to load, and an evidence pack your auditor can follow. SAP's own run posts.
It is a paid engagement with the scope and fee agreed up front; we do not run free trials. If it earns its place, the AUC ageing diagnostic across your estate comes next. Licence terms are agreed after the concierge, once you have seen it work on your own project.
Sold to the Financial Controller or Head of Fixed Assets, timed to a live trigger: an audit finding on componentisation or AUC, a revaluation cycle, or an S/4HANA migration. As-built data belongs to project delivery, so we ask for a named project-delivery co-sponsor.
Scope, outputs and fee are agreed in writing before work starts. Nothing is posted to your SAP systems.
- One completed project, componentised end to end
- Equipment linked to final assets; IAS 16 components and shares from a cost source
- Asset masters and a settlement rule for your SAP team to load
- Evidence pack: source and basis on every line, totals to the cent, audit trail
- Then, optionally, an AUC ageing diagnostic across the estate
- A written note on what to fix first
Pilot by fixed-fee SOW. Contact us.
There is no public price list yet. The concierge and the 30-day pilot are each a fixed fee agreed in a written statement of work before any work starts. We quote on the first call. There is no free trial; a walkthrough on synthetic data is free.
Licence terms follow the pilot. No licence price, SAP Store price or discount is published, because none has been decided.
The questions controllers actually ask.
Doesn't S/4HANA already reconcile this?
It removed the FI-AA-to-GL subledger reconciliation. The step between a finished project and the final fixed assets is still manual: which equipment the project created, the equipment-to-asset link (a hand-set field, one-to-one at best), and the assets, components and shares it becomes. That is what Attesta decides and evidences.
SAP now proposes settlement rules with generative AI. Why would I need Attesta?
As we understand SAP's public material, S/4HANA Cloud Private Edition can propose settlement receivers and percentages from project context. If you run that edition, try it. We have found no evidence that it reads the as-built equipment list or applies component templates, or that it ties each line to a cost source and keeps an evidence pack your team can attach to the asset in SAP; that is where Attesta differs. We understand it is not available on ECC or on-premise S/4HANA, where the rule is typed by hand. We have not benchmarked SAP's proposal against ours, so we would rather compare the two on one of your completed projects than argue it here.
Will this touch my SAP core or my postings?
No. It runs beside your SAP system and never touches the core. Today it runs standalone in your environment (container); the BTP edition is designed but not yet deployed or tested. The diagnostic is read-only. Attesta never posts: it exports asset masters and a settlement rule, and SAP's own run posts.
We're on ECC, not S/4. Does it still work?
Yes, through CSV file exchange today. A direct ECC connector is planned, not built. The engines are backend-neutral, so you are not gated on finishing your migration.
Our EAM data is messy, and half of it lives outside SAP.
That's the case it's built for. Rules carry the deterministic bulk; a transparent model that learns from your approvals suggests matches for messy non-SAP descriptions, with an auditable reason; your team approves. Non-SAP asset data comes in as CSV today.
Who owns this budget — finance or engineering?
Finance. The economic buyer is the Financial Controller, because the value is control hygiene and audit evidence. We time the engagement to a funded line: an audit finding, a revaluation cycle, or a migration. As-built data belongs to project delivery, so we ask for a named co-sponsor there.
Can we try it free?
A walkthrough on synthetic data is a free demo. A pilot or the concierge on your own project is paid; scope and fee are agreed in writing first.
What does it not do?
Book depreciation only: no tax books, no foreign-currency translation, no leases, no borrowing-cost computation. One currency and one company code per asset under construction. English only. Nine lifecycle actions (retire, transfer and others) have no screen and are refused in the pilot. No single sign-on in the standalone edition. The security page lists the rest.
Who owns the accounting outcome?
You do. Attesta is decision-support tooling — it proposes, apportions, and evidences, but your finance team and your advisors own the capitalisation decisions, the resulting financial statements, and their compliance. Every proposal is approved by a person and Attesta never posts; nothing is automated behind your back. Attesta is not accounting, tax, audit, or legal advice.
See what your last completed project should have become.
A 30-minute fit call. A walkthrough on synthetic data is free. If it's a fit, we scope a paid concierge on one completed project, then the diagnostic across your estate.
Request a fit call