Skip to main content
Pennylane is a French financial and accounting management solution, available as SaaS.

​
Prerequisites

You need to have a valid Pennylane account and admin rights on Hyperline.

​
Setup

1

In Hyperline, navigate to the Settings > Integrations page

2

Click Connect on the Pennylane card

3

Authenticate on Pennylane

If you are not already logged into Pennylane, enter your Pennylane credentials to proceed.
4

Select the company you wish to connect

Select and authorize the company you want to use.
5

That's it!

Your Hyperline account is ready to send invoices and credit notes.

​
Reconcile Hyperline and Pennylane customers

If you already have customers in Pennylane, link them with the corresponding customers in Hyperline. Open Settings > Integrations > Pennylane and click Import customers mapping under Customers mapping to contact support for help with the import.

​
Synchronization

When you connect your Pennylane account, Hyperline automatically sends invoices with their complete details (including line items and PDF file).
Hyperline only exports invoices created in Hyperline to Pennylane. Invoices imported from Pennylane into Hyperline (or linked to Hyperline-managed subscriptions) are not re-exported to avoid duplication and data conflicts.
If you use Stripe Payments or GoCardless with Hyperline, you also must connect them directly to your Pennylane account to ensure proper enrichment and reconciliation flow in Pennylane.
By default, only invoices and customers created after the connection date will sync. If you need to push older data to Pennylane, please contact our support team.

​
Customer synchronization

Hyperline supports 2 modes of synchronization for customers:
  • no synchronization: customers are not synchronized with Pennylane.
  • from Hyperline to Pennylane: customers created in Hyperline are automatically created in Pennylane with their details.
Alternatively, you can manually link a Pennylane customer to a Hyperline customer. On the Hyperline customer page, click the Edit button in the Integrations section, then paste either the Pennylane customer ID or the URL to the Pennylane customer page.

​
Payment synchronization

Hyperline supports 3 modes of synchronization for payments:
  • no synchronization: payments are not synchronized with Pennylane.
  • from Hyperline to Pennylane: Hyperline automatically creates payments in Pennylane and associates them with the corresponding invoice. Due to a Pennylane API limitation, only payments done using Stripe or GoCardless can be synced.
  • from Pennylane to Hyperline: payments created in Pennylane are automatically created in Hyperline, and the status of the invoice is updated accordingly.
The synchronization delay is 5 minutes maximum.

​
Map invoice properties to analytical categories

Use Mapping > Invoice to send invoice custom properties from Hyperline to Pennylane analytical categories. Each property maps to a Pennylane category group, and each property value maps to a category within that group. Before configuring a mapping, create a text or single-select custom property available on invoices in Hyperline, and create the category group and categories in Pennylane. Other property types are not supported.
  1. Open Settings > Integrations > Pennylane.
  2. Under Mapping > Invoice, click Add mapping.
  3. Select the invoice property under Hyperline field and the analytical group under Pennylane field. Use a different property and group for each mapping.
  4. Click Configure value mapping below the Pennylane selector.
  5. Click Add value mapping, enter or select a Property value, and select its Category. For text properties, values must match exactly, including capitalization. Add a row for each value your invoices use.
  6. Click Done. At least one complete row is required. Each property value can appear only once within the mapping.
  7. Enable Required if an invoice must have a value for this property to sync.
  8. Click Save changes on the integration settings page to save the configuration. Done only confirms the modal’s entries.

Example 💡

Map the Hyperline invoice property Region to the Pennylane group Sales region, then map EU to Europe. An invoice with EU receives a 100% allocation to Europe within that group.

​
How category mappings sync

  • Each matching value assigns 100% to one category in its group. Splitting an allocation across several categories in the same group is not supported.
  • For a mapped group with a matching value, Hyperline replaces the existing allocation. Allocations in other groups remain unchanged.
  • An empty optional property leaves the group’s existing allocation unchanged. An empty required property blocks synchronization.
  • A non-empty value without a matching category mapping blocks synchronization, even when Required is off. Add the missing value mapping, then retry.
  • Changing the selected Hyperline property or Pennylane group clears its value mappings. Configure them again before saving.
To apply changes to invoices already in Pennylane, use Resync after saving the settings.
If Hyperline asks you to reconnect to load analytical categories, use Reauthorize in the integration’s actions menu and grant access in Pennylane. Existing connections may need this additional authorization before category groups can load.

​
Synchronization rules

Synchronization rules select the Pennylane revenue account for each invoice or credit note line. Use them when different products or tax treatments need different accounts.
  1. Open Settings > Integrations > Pennylane. In Synchronisation rules, open the rule count card or No rules configured, then click Add rule.
  2. Select the Invoicing entity if prompted and enter a descriptive Name.
  3. Under Applied on, add filters for the lines the rule should cover. You can filter by products, product type, coupons, currency, country, tax scheme, tax territory, tax rate class, billing interval, invoice types, or custom properties.
  4. Under Account configuration, select a Revenue account. Use Sync accounts from Pennylane to refresh the available accounts.
  5. Click Save changes.
A matching rule’s account takes precedence over the product account code. The selected account must exist in Pennylane’s chart of accounts; otherwise, synchronization fails with a missing-account error. See Product and account codes for Pennylane’s account-code format. Leave filters empty to create a default rule. At the same priority, a rule scoped to a matching product takes precedence over the default. Avoid overlapping rules with conflicting accounts.

Example 💡

Select your software subscription revenue account in a default rule, then add a rule filtered to your onboarding product with a separate services revenue account. Pennylane receives each line with the corresponding account.
Pennylane synchronization rules apply to invoice and credit note accounts. They do not select payment accounts or journals, or change your customer and payment synchronization modes.

​
Manage the integration

To reauthorize, reconfigure, resync, or disconnect this integration, see Manage connected integrations.

​
Product and account codes

Configure account codes on products in Hyperline without trailing zeros. For example, if your Pennylane account code is 7010301000, you should enter 7010301 in Hyperline.
Pennylane may display account codes with trailing zeros, but you should remove them when configuring the codes in Hyperline to ensure proper synchronization.

​
Troubleshooting sync errors

If a Pennylane sync fails, open the Pennylane integration issues page in Hyperline to review the latest error. Retry after you correct the data. Common causes include:
By default, only invoices, customers, and payments created after the Pennylane connection date are synchronized. If you need to push older data, contact support to request a backfill.
During some migrations, Pennylane can display an imported invoice as partially paid even when the invoice total is fully covered by payments. This usually comes from a header-total or reconciliation mismatch. Contact support with the invoice ID so the team can review the Pennylane response.