---
# System prepended metadata

title: New Lab x Membership Plans feature customization x 3rd party software Quickbooks integration

---

## :fire: Feature Requirements Document
# New Lab x Membership Plans feature customization x 3rd party software Quickbooks integration

### Feature Title: Quickbooks integration
---

### Feature general description
Introducing a simple, easy to use integration with 3rd party accountancy software (Quickbooks) to help New Lab's accountancy team connect their tool of choice with spaceOS.


### Problem statement
New Lab's accountancy team already uses a software of their choice. They would be struggling with using spaceOS right now, because it doesn't cover all of their needs (yet).

### Users (for whom is it going to be designed)
SpaceOS admins, who are New Lab accountants.

### Business value
==tbd==

### User value
Accountants can use software that they are most comfortable with while still benefitting from using spaceOS invoicing feature. No need for manual work connecting or copying data from spaceOS to Quickbooks.

### Real user scenarios
==ask @NewLab==
> [color=#FF742D] This will help a lot! :pray:
> [name=Tomek Omelan]




### Scope (more details, what does what, where, etc.)
A feature for spaceOS users with Admin role only.
Admin has to be able to turn on/off the integration (provide credentials).
Is it a one-way integration? (only sending invoices FROM spaceOS TO Quickbooks).
A easy way to assign spaceOS products (items on the invoice) with Quickbook accounts.

### Questions & constraints
1. It has to be one-way integration due to complexity of data.
2. Quickbooks API is the limit.
3. What happens in the following scenario: admin turns on the integration, issues invoices, then turns off the integration. What happens to the defined products within Quickbooks? What should happen when admin enables it again?
4. What is the approach to invoices issued before the integration?

:::info
:skull: Deadline: January 2020
:::
