Quick start: compress a Basware PDF in about 2 minutes

If your real goal is simply make this Basware PDF smaller so it is easier to upload, review, and archive, this workflow is usually enough:

  1. Start with the invoice packet, supplier onboarding PDF, PO support file, approval bundle, compliance certificate, or procurement backup you actually plan to keep.
  2. Open Compress PDF.
  3. Upload the file and choose Medium compression first.
  4. Download the smaller result and compare the new size with the original.
  5. Preview the weak spots: supplier names, invoice numbers, dates, totals, VAT rows, PO references, signatures, and the faintest scanned text.
  6. If the file came from a scanner or phone capture, run OCR PDF so the final document is searchable as well as smaller.
  7. If the packet still feels bulky, split the appendix, extract only the useful pages, or delete duplicates before trying stronger compression.
Best default for Basware prep: start with Medium compression. It usually gives the safest balance between a lighter file and a document that still feels dependable when AP, procurement, finance, or audit teams open it later.

Why Basware PDFs get bulky

Basware workflows collect the kinds of PDFs that grow quietly. An invoice export is paired with purchase-order support. A supplier form is rescanned because someone wanted a signature page. An approval memo, statement excerpt, or compliance certificate gets attached just in case the next reviewer asks for it. By the time the packet feels complete, the PDF often carries much more image weight than useful proof.

Smaller PDFs help because they move more smoothly through ordinary AP and procurement work. They upload faster, preview more cleanly, and create less friction when someone needs to verify a supplier name, invoice number, due date, VAT field, total, PO reference, or approval comment. The goal is not to erase detail. The goal is to remove wasted weight while keeping the record trustworthy.

  • Faster upload and review: especially helpful when several support files need to be attached in one session.
  • Cleaner approval flow: lighter PDFs are easier for buyers, AP staff, controllers, and auditors to open quickly.
  • Better archive quality: smaller files are easier to store, resend, and reuse later.
  • Less scan bloat: scanned supplier paperwork and certificate pages often contain much more image weight than they need.
  • More flexible follow-up work: compact PDFs are easier to split, crop, OCR, merge, and compare later.
Simple rule: compress the file enough to remove drag, not so hard that invoice numbers, VAT rows, supplier names, signature blocks, or approval notes become harder to trust.

What file size should you aim for?

There is no single perfect number for every Basware workflow, so practical ranges are more useful than chasing the tiniest result possible. You want a file that feels easy to open and review while still looking like dependable business support.

Document type Practical target What to protect
Text-heavy invoice, supplier form, or PO support PDF < 1MB to 2MB Supplier names, invoice numbers, dates, totals, tax fields, and short approval notes
Invoice packet or mixed procurement support file 1MB to 3MB PO references, line-item tables, signatures, and the support details the next reviewer still needs
Approval bundle, statement excerpt, or scanned certificate set 2MB to 5MB Faint text, stamps, handwritten notes, certificate numbers, and the smallest useful details on scanned pages
Over 5MB Usually needs cleanup At that point, trimming page waste often works better than compressing harder

If a straightforward invoice or supplier-support PDF is still much larger than these ranges, the real problem is often scan waste, duplicate pages, large screenshots, or a packet that is trying to serve too many audiences at once. Compression helps, but structure often matters just as much.

Which compression level should you choose?

Start conservative and only push harder if the file stays too large after one sensible pass.

  • Low compression: best when the PDF is already clean or contains delicate text, dense tables, or signatures that cannot afford much softening.
  • Medium compression: the best default for most Basware PDFs because it balances size reduction and readability.
  • High compression: useful for scan-heavy packets or phone-captured paperwork, but it should always be followed by a real quality check.
Practical rule: if the PDF contains VAT fields, invoice numbers, small table text, or faint scan detail, test Medium before you do anything more aggressive.

Step-by-step: shrink a Basware PDF with LifetimePDF

  1. Save the final Basware-ready file. Start with the version the next person actually needs, not a giant packet with every backup page still attached.
  2. Open LifetimePDF Compress PDF. This is the quickest way to remove unnecessary weight before upload or archive.
  3. Upload the PDF and start with Medium. For most invoices, supplier forms, PO support files, approval PDFs, and procurement attachments, that is the safest first pass.
  4. Download the smaller copy and compare the size change. You want a lighter file, not a damaged record.
  5. Review the details that fail first. Check supplier names, invoice numbers, due dates, totals, VAT rows, PO references, signatures, and the faintest scan text.
  6. Use OCR if the file is image-only. Open OCR PDF so the document stays searchable after cleanup.
  7. Trim page weight only if needed. If the PDF is still too heavy, use Delete Pages, Extract Pages, Crop PDF, or Split PDF before trying stronger compression.

Shortcut: if you only need one practical workflow, do this in order: compress → review → OCR if scanned → trim pages only if the packet is still too large.

Compress PDF OCR PDF Delete Pages

Best approach for common Basware document types

Invoices and AP support packets

Text-heavy invoices usually compress well. Start with Medium and focus your review on the supplier name, invoice number, invoice date, due date, totals, tax rows, and any payment references. If the file still feels oversized, the problem is often a scan or export issue rather than the invoice itself.

PO support and procurement attachments

These files can mix quote pages, approval notes, pricing tables, screenshots, and supporting comments. Medium compression is usually the safest first choice, but still review the smallest text, item tables, reference numbers, and supporting notes before keeping the smaller version.

Supplier onboarding and compliance PDFs

Supplier setup files, tax forms, bank letters, and certificates often look simple while carrying hidden file weight from scans and rescans. Preserve names, registration numbers, dates, signatures, and certificate details. If the PDF is image-heavy, OCR and crop tools usually help more than aggressive compression alone.

Approval bundles and statement excerpts

These often become bloated because they include pages nobody actually needs. Before turning the compression level up, ask whether the next reviewer needs the full packet, the whole thread, or just the narrow excerpt that proves the invoice and approval context. Smaller scope usually beats harsher compression.

What to clean up before compressing harder

If Medium compression barely moves the size, the PDF probably has a structure problem rather than a compression problem.

  • Delete duplicate pages: common after merging invoices, certificates, statement snippets, and support material from several sources.
  • Crop empty scan borders: oversized white margins add weight without adding value.
  • Extract only the useful section: a reviewer may only need the invoice, summary page, or one certificate page, not the whole packet.
  • Split large packets: one primary file and one appendix often work better than one bulky all-in-one PDF.
  • Run OCR on scans: especially useful for photographed paperwork, faded printouts, and rescanned supplier documents.

In a lot of AP and procurement workflows, sending less PDF solves the problem faster than sending the same bloated file at a harsher compression level.

How to keep review-critical details readable

Basware PDFs are only useful if someone can still trust the details after cleanup. Before you keep the smaller file, review the parts that matter most:

  • Supplier legal name and remit-to details
  • Invoice number, issue date, due date, and PO reference
  • Subtotal, VAT or tax amount, and final total
  • Line-item tables, certificate numbers, or statement references
  • Approval notes, signatures, and stamped fields
  • The faintest text on photographed receipts or rescanned paperwork
Good test: if a tired reviewer could still confirm the supplier, the amount, the date, and the approval context without zooming in everywhere, the compression is probably fine.

Workflow habits that reduce PDF bloat

The easiest way to keep Basware PDFs manageable is to stop extra weight before it piles up.

  • Keep the final upload file separate from the giant internal backup packet.
  • Use direct PDF exports when available instead of print-to-PDF after every handoff.
  • Ask for cleaner scans when supplier documents are blurry the first time.
  • Merge only the pages the next reviewer really needs.
  • Run OCR early on paper-origin documents so later searches do not depend on image-only files.
  • Archive a clean version once instead of repeatedly rescanning the same record.

None of this is glamorous, but it cuts friction across approvals, month-end support, supplier follow-up, and audit prep.

If you are cleaning a Basware file, these tools and guides usually help next:

FAQ (People Also Ask)

How do I compress a PDF for Basware?

Upload the Basware-ready PDF to a PDF compressor, start with Medium compression, and preview the smaller result before you keep it. For most Basware workflows, Medium compression is the safest starting point because it reduces size while keeping supplier names, invoice numbers, PO references, VAT fields, totals, and approval notes readable.

What file size should I aim for with Basware PDFs?

Under 2MB is a strong target for text-heavy invoices, supplier forms, and PO support PDFs. Scan-heavy approval bundles, certificates, and mixed procurement packets often work better around 2MB to 5MB as long as the smallest useful details still look clear.

Should I run OCR on scanned Basware documents before compressing them?

Usually yes if the file came from a scanner or phone camera and the text is not selectable. OCR helps invoice packets, supplier documents, procurement backups, and audit support stay searchable, easier to review, and easier to reuse later.

Will compression make invoice numbers or VAT fields blurry?

It can if you compress too aggressively. That is why Medium compression is usually the best first move. Always review supplier names, invoice numbers, dates, PO references, VAT fields, totals, and the faintest scanned text before keeping the smaller PDF.

What if my Basware PDF is still too large after compression?

Delete duplicate or blank pages, crop empty scan borders, split one oversized packet into smaller PDFs, extract only the pages the next reviewer needs, or run OCR on image-only paperwork. In many procurement and AP workflows, sending less PDF works better than compressing the same bloated file harder.

Ready to clean the file up? Start with the compressor, then use OCR or page tools only if the PDF still carries more weight than the next reviewer needs.

Compress PDF Now OCR PDF Get Lifetime Access