KPL-2374
GitHub WeFact

Keep GitHub and WeFact updated automatically.

Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it. This connector fixes that, and we build it on request: what happens in GitHub lands in WeFact by itself, in the shape WeFact expects. Tell us what you need and we agree exactly what should travel.

InvoicesContactsVAT
The problem

What this connector takes off your hands

  • Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it.

  • Today you type the postings in by hand, pick the right account and VAT rate per line, and check afterwards whether it reconciles.

What you get out of it

What GitHub to WeFact saves you

  • Book every task you finish in GitHub straight into WeFact.
  • Book every new row in GitHub straight into WeFact.
The link

What travels across the link

Everything this connector moves between GitHub and WeFact, and how often.

  1. Invoices

    to WeFact automatically

    Every sale becomes an invoice in WeFact with its own line items and the order number as reference, so you can trace it back without retyping.

  2. Contacts

    to WeFact automatically

    The customer is recorded as a contact in WeFact or reused by email, so no duplicate relation appears.

  3. VAT

    to WeFact automatically

    The VAT rate is set per line, and foreign sales get the rate of the destination country, ready for your OSS return.

Both sides

What each side expects

GitHub and WeFact do not describe the world the same way. This is what has to line up.

WeFact

An accounting package wants to know, per line, which ledger account and VAT rate apply, and wants the customer on file as a relation.

In four steps

Setting it up

  1. 01

    Request the connector

    Let us know you want to link GitHub to WeFact. We get in touch within 24 hours with a timeline.

  2. 02

    We agree what should travel

    Together we settle what should travel out of GitHub. An accounting package wants to know, per line, which ledger account and VAT rate apply, and wants the customer on file as a relation.

  3. 03

    We build and test

    You see the connector run on a few test records before anything becomes final.

What you need

  • An account with edit rights, and the list or project it should land in.
  • An administration you administer, plus clarity on the ledger account you want used.

Where it runs

On app.schakel.app, with your own Schakel account. No webshop required.

We build this connector on request. Tell us what you need and we reply within 24 hours.

Common questions

Can you connect GitHub to WeFact?

Yes. Schakel connects through the official APIs of GitHub and WeFact, so you install nothing on your own server and nothing travels outside those two parties.

Which VAT rate do my sales get in WeFact?

The rate is set per line: 21%, 9% or 0%. Sales to Belgium and other EU countries get the rate of the destination country, ready for your OSS return.

Are commission and fees booked separately in WeFact?

Yes. Commission, shipping and other fee types each land on their own ledger account in WeFact, rather than in one lump sum, so your margin stays readable.

From what moment in GitHub does something reach WeFact?

As soon as you add or finish the row or task in GitHub that you chose as the trigger, it reaches WeFact.

What does connecting GitHub and WeFact cost?

You start free and only pay once the connector is really running. After that the same tiers apply as for any other connector, based on how much runs through it each month.

How often does GitHub sync with WeFact?

That depends on your tier: hourly on the free tier up to real time on the unlimited tier. You can always start a sync yourself as well.

What happens to a return or refund in WeFact?

A return becomes a credit invoice in WeFact for the amount actually refunded, not for the whole order, so nothing needs correcting afterwards.

What if GitHub or WeFact is briefly unavailable?

Nothing gets lost. Schakel retries later and the log shows exactly what happened, so at most you notice something coming through a little later.

Missing something you need?

Tell us what GitHub and WeFact should do for you. If it is not in here yet, that is usually because nobody has asked. We build on request and we reply within 24 hours.