Most formatting errors in the SAP Ariba portal come from unsupported file types, character encoding mismatches, rich text fields that strip styling, and broken tables pasted from Word. Fix them by converting files to Ariba-approved formats (PDF, XLSX, DOCX), pasting as plain text into text fields, and validating attachments before the deadline. Always test in the supplier preview first.
Why Ariba rejects or mangles your formatting
Ariba isn't a word processor. Its response fields are HTML-based form inputs with strict limits, and its attachment engine validates file types and sizes server-side. When your carefully styled proposal looks broken on submission, it's usually one of these culprits:
- Unsupported or mislabeled file types — Ariba blocks executables, some compressed archives, and files with mismatched extensions.
- Character encoding errors — smart quotes, em dashes, and emoji from Word paste in as garbage characters or trigger validation failures.
- Rich text limits — many Ariba text fields accept only plain text or limited HTML, so bold, bullets, and headers vanish.
- Field character caps — answers silently truncate when you exceed the field limit (often 4,000 or 16,000 characters).
- Table corruption — Word tables pasted into Ariba lose structure entirely.
Most teams get this wrong by drafting everything in Word and pasting at the last minute. The portal behaves differently than your desktop, and the difference shows up at the worst time.
Step-by-step fixes for common Ariba formatting errors
1. Use Ariba-approved file formats
Stick to formats SAP Ariba reliably accepts:
| File type | Use it for | Notes |
|---|---|---|
| Final proposal documents | Flatten before upload to lock formatting | |
| DOCX | Editable submissions buyers requested | Avoid legacy .doc |
| XLSX | Pricing sheets, BOQs | Don't upload .csv if a template is provided |
| PNG/JPG | Diagrams, org charts | Embed in PDF when possible |
Avoid .zip unless the event explicitly allows it. Some Ariba realms reject archives outright. Check SAP's supplier file requirements within your specific event, since admins can tighten defaults.
2. Kill smart characters before pasting
Word auto-converts straight quotes to curly quotes and double hyphens to em dashes. Ariba's text fields can choke on the encoding. Before pasting into any response box:
- Turn off AutoCorrect in Word (File > Options > Proofing > AutoCorrect Options).
- Or paste through a plain-text editor like Notepad to strip all formatting.
- Re-add line breaks manually in the Ariba field.
A quick find-and-replace clears the worst offenders:
“ ” → "
‘ ’ → '
— → -
… → ...
3. Respect rich text field limits
Ariba response fields vary. Some accept basic HTML; many don't. If your bullets and bold disappear:
- Click the field's expand icon to see if a rich-text toolbar exists.
- If no toolbar, write in plain text with manual numbering (1., 2., 3.) and blank lines for spacing.
- Move anything truly formatted — tables, styled sections — into a PDF attachment and reference it in the text field.
4. Stop tables from breaking
Pasting Word tables into Ariba text fields almost never works. The same root cause breaks exports, and the issues that cause pricing tables to break when exporting from Word to PDF apply here too. Instead:
- Put pricing in the Ariba line-item grid if the event provides one.
- Attach complex tables as XLSX or a flattened PDF.
- Never rely on a pasted table rendering correctly in the buyer's view.
5. Check character counts
When an answer truncates, you've hit the field cap. Ariba rarely warns you clearly. Count characters in Word (Review > Word Count) before pasting, and split long responses across the intended fields rather than cramming everything into one box.
Validate before you submit
The single most reliable fix is previewing. Ariba supplier accounts let you review your response before final submission.
- Open the Review Response or Validate option.
- Confirm every text field renders as intended — no garbage characters, no missing bullets.
- Open each attachment from inside the portal, not from your local drive, to confirm it uploaded intact.
- Verify file sizes are under the event limit (commonly 100 MB per file, but admins set this).
If an attachment fails to appear after upload, that's a separate but related problem — see how to troubleshoot the missing attachments error in SAP Ariba before assuming it's a formatting issue.
Browser and session gotchas
Ariba is finicky about browsers and timeouts. A few practical fixes:
- Use a supported browser. Recent Chrome or Edge versions work best. Older Firefox builds sometimes mangle uploads.
- Clear cache if fields render oddly or buttons don't respond.
- Disable browser extensions — ad blockers and PDF viewers can intercept uploads.
- Watch the session timer. Ariba sessions expire (often 30 minutes idle). A timeout mid-upload can corrupt a partial submission. Save drafts frequently.
Build formatting-safe proposals upstream
The cleanest fix happens before Ariba ever sees your content. Standardizing where you draft prevents most portal surprises. If your team debates tooling, this comparison of Word vs Google Docs vs dedicated RFP software covers how each handles export and portal compatibility. Consistent source files also help when unifying voice across multiple SME contributions, which reduces the copy-paste chaos that introduces encoding errors in the first place.
Keep a portal-ready version of every answer: plain text for response fields, flattened PDFs for attachments. Build it during drafting, not at 11 PM before a noon deadline.
Key takeaways
- Convert files to Ariba-approved formats (PDF, DOCX, XLSX) and flatten PDFs to lock formatting.
- Strip smart quotes, em dashes, and other special characters before pasting into text fields.
- Assume response fields are plain text; move tables and styling into attachments.
- Always use the Review/Validate preview and open every attachment from inside the portal.
- Use a supported browser, save often, and watch the session timeout.
- Prepare portal-ready content during drafting to avoid last-minute formatting failures.