Opis

Patsch9 Accounting Bridge connects WooCommerce with the Lexware Office Public API. It can create and manage invoices and credit notes from WooCommerce orders, process synchronization jobs through a queue, and make invoice documents available in the customer account.

The plugin declares WooCommerce High-Performance Order Storage (HPOS) compatibility and uses WooCommerce order CRUD APIs for order data.

Trademark notice: WooCommerce® is a trademark of Automattic Inc. Lexware® and Lexware Office are trademarks or product names of Haufe-Lexware GmbH & Co. KG. This is an independent third-party extension and is not produced, sponsored, or endorsed by Automattic or Haufe-Lexware.

Features

Automatic or manual invoice creation from WooCommerce orders.
Read-only reconciliation of historical WooCommerce orders with existing Lexware invoices using the order number in the invoice introduction plus gross-total verification.
Exact email based Lexware customer matching.
Queue-based processing with deduplication and locking.
Action Scheduler integration with WP-Cron fallback.
Credit notes based on the original Lexware invoice snapshot.
Invoice download and WooCommerce My Account integration.
WooCommerce email integration.
Optional handling of rental deposit metadata without a hard dependency on a rental plugin.
HPOS compatibility.
Conservative handling of ambiguous write responses to reduce duplicate accounting documents.

Requirements

WordPress 6.9 or newer.
PHP 8.2 or newer.
WooCommerce 10.9.4 or newer.
A Lexware Office account with Public API access enabled.
A valid Lexware API key.

Configuration

For improved secret handling, the Lexware API key can be stored outside the WordPress database in wp-config.php:

define( 'PATSACBR_LEXWARE_API_KEY', 'YOUR_API_KEY' );

The constant takes precedence over a key stored in WordPress options.

External Services

Lexware Office Public API

The Lexware Office Public API at https://api.lexware.io/v1/ is a core service required by this plugin. Depending on the action, data sent to Lexware may include customer names, billing and shipping addresses, email addresses, order items, prices, taxes, shipping or fee items, and order references. The API key is transmitted for authentication.

Developer portal: https://developers.lexware.io/
API documentation: https://developers.lexware.io/docs/
Public API terms: https://agb.lexware.de/lexware-office/public-api-lizenz–und-nutzungsbedingungen
Privacy policy: https://www.lexware.de/datenschutz/

The site operator is responsible for providing the required privacy information and for complying with the applicable Lexware terms.

Privacy

API logging is disabled by default on new installations. When logging is enabled, known personal-data fields are masked and complete API response bodies are not stored permanently.

Compatibility

WooCommerce HPOS compatibility is declared.
WooCommerce order data is accessed through the WooCommerce CRUD API.
Action Scheduler is used when available; WP-Cron is used as a fallback.
Plugin-owned declarations, hooks and stored data use the unique PATSACBR_ / patsacbr_ prefix. Data from pre-directory builds is migrated during upgrade.

Instalacija

Install and activate WooCommerce.
Upload and activate this plugin.
Configure the Lexware API key.
Configure the order statuses and synchronization options that should trigger invoice processing.

Pitanja i odgovori

Do I need a Lexware account?: Yes. An active Lexware Office account with Public API access is required.
What data is transferred?: The customer, order, line-item, price, tax, and reference data required to create or retrieve contacts and accounting documents is transferred to the Lexware Office Public API.
Is plugin data removed when the plugin is deleted?: Not by default. Full data cleanup on uninstall must be explicitly enabled in the plugin settings.
Which languages are supported?: English is the source language. A complete German (de_DE) translation is bundled, including customer emails and invoice text defaults for new installations. Existing custom invoice texts and saved email settings are preserved. Additional translations can be contributed at https://translate.wordpress.org/projects/wp-plugins/patsch9-accounting-bridge/.

Recenzije

Nema recenzija za ovaj dodatak.

Suradnici i Programeri

“Patsch9 Accounting Bridge for WooCommerce” je softver otvorenog koda. Sljedeće osobe su doprinijele ovom dodatku.

patsch9

Prevedite “Patsch9 Accounting Bridge for WooCommerce” na svoj jezik.

Zainteresirani ste za razvoj?

Pregledajte kôd, pogledajte SVN spremišteili se pretplatite na dnevnik razvoja od RSS.

Dnevnik promjena

2026.10.7

Read and sanitize manual invoice fields immediately after nonce verification, before acquiring the order lock. Reject array-valued request fields.
Run strict source and release-package Plugin Check on every pull request to main.
Includes the migration and order-lock fixes prepared for 2026.10.6; that release was blocked by Plugin Check.

2026.10.6

Protect legacy migration data and serialize invoice writes for each order. Add database regression tests.

2026.10.5

Recognize canonical Rental Engine deposit and payment-terms metadata while retaining support for historical orders.

2026.10.4

Uses English source strings and bundles a complete German translation.
Generates the complete translation template from source with WP-CLI.
Makes invoice defaults, administrator error emails, and settings examples translatable while preserving saved texts.
Handles translated confirmation messages safely without embedding them in JavaScript code.

2026.10.3

Addresses WordPress.org review findings: admin assets are enqueued, plugin-owned identifiers use a unique prefix, and admin notices are scoped to relevant screens.
Normalizes the minimum WordPress version header and migrates data from pre-directory builds.

2026.10.2

Adds manual start/restart controls and progress reporting for historical Lexware invoice reconciliation.

2026.10.1

Adds background reconciliation for orders that existed before the integration was active.
Existing Lexware invoices are linked only after an exact order-number match in the invoice introduction and gross-total verification.
Ambiguous matches and API lookup errors fail closed to prevent duplicate invoices.
Manual unlinking opts the order out of automatic historical relinking.

2026.10.0

First stable public release using the project-wide YYYY.M.PATCH versioning scheme.
Consolidates the functional and security changes from all previous internal prerelease versions through 1.3.6.
Revalidated API write handling, queue locking, credit-note logic, HPOS order access, and protected invoice downloads.
Accounting mappings and queue data are preserved on uninstall by default; destructive cleanup requires explicit opt-in.