https://docs.delftsolutions.nl/api.php?action=feedcontributions&feedformat=atom&user=Vincent 2026-04-03T20:28:59Z User contributions MediaWiki 1.39.3 https://docs.delftsolutions.nl/index.php?title=Postgres_issues&diff=698 2026-03-24T15:45:54Z

<p>Vincent: Created page with &quot;&#039;&#039;WIP&#039;&#039; When you suspect database/postgres issues causing degraded performance on a service, you can check the following: == Check blocking sessions == A function listing the sessions preventing a session from acquiring a lock - https://pgpedia.info/p/pg_blocking_pids.html == Lock monitoring == Viewing information on current locking state - https://wiki.postgresql.org/wiki/Lock_Monitoring == Postgres logging == Options for logging locking issues in postgres - h...&quot;</p> <hr /> <div>''WIP''<br /> <br /> When you suspect database/postgres issues causing degraded performance on a service, you can check the following:<br /> <br /> == Check blocking sessions ==<br /> <br /> A function listing the sessions preventing a session from acquiring a lock<br /> <br /> - https://pgpedia.info/p/pg_blocking_pids.html<br /> <br /> == Lock monitoring ==<br /> <br /> Viewing information on current locking state<br /> <br /> - https://wiki.postgresql.org/wiki/Lock_Monitoring<br /> <br /> == Postgres logging ==<br /> <br /> Options for logging locking issues in postgres<br /> <br /> - https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-LOCK-WAITS</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=697 2026-03-24T15:37:56Z

<p>Vincent: </p> <hr /> <div>== Strategy ==<br /> * [[Flow metrics|Flow metrics]]<br /> * [[12%-time|12%-time]]<br /> <br /> == Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking bonus|Booking bonus]]<br /> * [[booking wages|Booking wages]]<br /> * [[booking quarterly hosting invoice|Booking quarterly hosting invoice]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> * [[invoice approval|Process for approving invoices (/filed receipts)]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Work Process ==<br /> <br /> * [[Definition of done|Definition of Done]]<br /> * [[Incident Handling|Incident Handling]]<br /> * [[SRE Maintenance|SRE Maintenance]]<br /> * [[Release checklist|Release checklist]]<br /> * [[Handover]]<br /> <br /> == Internal Process ==<br /> * [[timetracking|Timetracking process]]<br /> * [[Starting work for a new client]]<br /> * [[12 percent|12% time]]<br /> * [[Annual leave|Annual leave]]<br /> * [[Bonus allocation|Bonus allocation]]<br /> * [[Calamity leave|Calamity leave]]<br /> * [[Overtime|Overtime]]<br /> * [[Retrospectives|Retrospectives]]<br /> * [[Sick leave|Sick leave]]<br /> * [[Training and self-study|Training and Self-Study]]<br /> * [[Daily|Daily]]<br /> <br /> == Projects ==<br /> <br /> * Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]<br /> * [[border update|Process for updating a border]]<br /> * [[border reboot|Reboot border without downtime]]<br /> * [[ceph|Common Ceph commands]]<br /> * [[WS Proxmox node reboot|Reboot WS Proxmox node without downtime]]<br /> * [[Resize VM Disk]]<br /> * [[SRE tools]]<br /> * [[Enroll Mac in Kerberos]]<br /> * [[New Mac Setup]]<br /> * [[Creating a VM on Hetzner]]<br /> * [[Rebooting VM]]<br /> * [[Rebooting Offsite]]<br /> * [[ssh-fingerprints|Verifying SSH fingerprints]]<br /> * [[Removing VM]]<br /> * [[Install a new Disk in Server]]<br /> * [[Setting Up Wildcard Subdomains with SSL on a Debian Application]]<br /> * [[s3 bucket backup|Get credentials to backup S3 bucket to Zombie]]<br /> * [[Hardware Incident Response: Memory Slot Failure on banshee]]<br /> * [[dfz switch setup|DFZ Switch setup]]<br /> * [[Update Zulip Server version]]<br /> * [[update-sentry|Update Sentry]]<br /> * [[iDRAC: Upload a new pem certificate for automatic updates]]<br /> === SLA ===<br /> * [[Response for Backup Service being down for an extended period of time]]<br /> * [[postgres issues|Analyzing postgres performance]]<br /> <br /> == Other ==<br /> <br /> * [[stack|Greenfield stack]]<br /> * [[standard tools|Standard Tools]]<br /> * [[list of unfurl debuggers|List of unfurl debuggers]]<br /> * [[Recommended suppliers]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Update-sentry&diff=678 2025-11-07T16:16:47Z

<p>Vincent: </p> <hr /> <div>'''Context:'''<br /> This procedure was written at the time of Sentry 25.10.0, and applies to upgrades performed on the sentry server.<br /> <br /> '''Important Notes'''<br /> * It is possible to skip version while upgrading, except for Hard-Stops, which you need to install before updating to newer releases, [https://develop.sentry.dev/self-hosted/releases/#hard-stops see Sentry docs on hard stops]<br /> * Always consult the official [https://develop.sentry.dev/self-hosted/releases/ Sentry upgrade documentation] first.<br /> <br /> == Pre-upgrade Steps ==<br /> # Read the [https://github.com/getsentry/self-hosted/releases release notes] and prepare accordingly if some specific actions need to be taken<br /> # Schedule and announce the maintenance window<br /> # Create a maintenance period in Zabbix<br /> # Create a backup and/or snapshot<br /> <br /> == Upgrade Procedure ==<br /> # Navigate to `/opt/sentry`<br /> # Run `git fetch --tags`<br /> # Run `git checkout &lt;tag of release you want to update to&gt;`<br /> # Compare `./sentry/config.yml` with `./sentry/config.example.yml`, amend where necessary<br /> # Compare `.sentry/sentry.conf.py` with `./sentry/sentry.conf.example.py`, amend where necessary<br /> # Compare `./.env.delftsolutions` with `./.env` , amend where necessary<br /> # Until we use Podman, Sentry finally lowers the docker-compose version requirement, or until the below steps stop working:<br /> ## In file install/dc-detect-version.sh need to modify the dcr variable (short for docker compose run, is boilerplate) command to remove the --pull flag<br /> ## In file install/_min-requirements.sh lower the min required version to at most 2.26.1 (or what version is currently installed)<br /> # Run `./install.sh`<br /> # Run `docker compose --env-file .env.delftsolutions up -d`<br /> <br /> == Post-upgrade Steps ==<br /> # Go to Issues &gt; Alerts<br /> # Pick an alert rule (the kaboom-api rule is suggested), go to the alert edit page<br /> # On the page, click the button &quot;Send Test Notification&quot;, announce the notifications were as expected when they come in<br /> # Once you've made sure everything is running as expected remove the snapshot and maintenance period</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Update-sentry&diff=677 2025-11-07T16:10:01Z

<p>Vincent: Created page with &quot;&#039;&#039;&#039;Context:&#039;&#039;&#039; This procedure was written at the time of Sentry 25.5.1, and applies to upgrades performed on the sentry server. &#039;&#039;&#039;Important Notes&#039;&#039;&#039; * It is possible to skip version while upgrading, except for Hard-Stops, which you need to install before updating to newer releases, [https://develop.sentry.dev/self-hosted/releases/#hard-stops see Sentry docs on hard stops] * Always consult the official [https://develop.sentry.dev/self-hosted/releases/ Sentry upgrade doc...&quot;</p> <hr /> <div>'''Context:'''<br /> This procedure was written at the time of Sentry 25.5.1, and applies to upgrades performed on the sentry server.<br /> <br /> '''Important Notes'''<br /> * It is possible to skip version while upgrading, except for Hard-Stops, which you need to install before updating to newer releases, [https://develop.sentry.dev/self-hosted/releases/#hard-stops see Sentry docs on hard stops]<br /> * Always consult the official [https://develop.sentry.dev/self-hosted/releases/ Sentry upgrade documentation] first.<br /> <br /> == Pre-upgrade Steps ==<br /> # Read the [https://github.com/getsentry/self-hosted/releases release notes] and prepare accordingly if some specific actions need to be taken<br /> # Schedule and announce the maintenance window<br /> # Create a maintenance period in Zabbix<br /> # Create a backup and/or snapshot<br /> <br /> == Upgrade Procedure ==<br /> # Navigate to `/opt/sentry`<br /> # Run `git fetch --tags`<br /> # Run `git checkout &lt;tag of release you want to update to&gt;`<br /> # Compare `./sentry/config.yml` with `./sentry/config.example.yml`, amend where necessary<br /> # Compare `.sentry/sentry.conf.py` with `./sentry/sentry.conf.example.py`, amend where necessary<br /> # Compare `./.env.delftsolutions` with `./.env` , amend where necessary<br /> # Run `./install.sh`<br /> # Run `docker compose --env-file .env.delftsolutions up -d`<br /> <br /> == Post-upgrade Steps ==<br /> # Go to Issues &gt; Alerts<br /> # Pick an alert rule (the kaboom-api rule is suggested), go to the alert edit page<br /> # On the page, click the button &quot;Send Test Notification&quot;, announce the notifications were as expected when they come in<br /> # Once you've made sure everything is running as expected remove the snapshot and maintenance period</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=676 2025-11-07T08:06:52Z

<p>Vincent: /* SRE */</p> <hr /> <div>== Strategy ==<br /> * [[Flow metrics|Flow metrics]]<br /> * [[12%-time|12%-time]]<br /> <br /> == Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking bonus|Booking bonus]]<br /> * [[booking wages|Booking wages]]<br /> * [[booking quarterly hosting invoice|Booking quarterly hosting invoice]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> * [[invoice approval|Process for approving invoices (/filed receipts)]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Work Process ==<br /> <br /> * [[Definition of done|Definition of Done]]<br /> * [[Incident Handling|Incident Handling]]<br /> * [[SRE Maintenance|SRE Maintenance]]<br /> * [[Release checklist|Release checklist]]<br /> * [[Handover]]<br /> <br /> == Internal Process ==<br /> * [[timetracking|Timetracking process]]<br /> * [[Starting work for a new client]]<br /> * [[12 percent|12% time]]<br /> * [[Annual leave|Annual leave]]<br /> * [[Bonus allocation|Bonus allocation]]<br /> * [[Calamity leave|Calamity leave]]<br /> * [[Overtime|Overtime]]<br /> * [[Retrospectives|Retrospectives]]<br /> * [[Sick leave|Sick leave]]<br /> * [[Training and self-study|Training and Self-Study]]<br /> * [[Daily|Daily]]<br /> <br /> == Projects ==<br /> <br /> * Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]<br /> * [[border update|Process for updating a border]]<br /> * [[border reboot|Reboot border without downtime]]<br /> * [[WS Proxmox node reboot|Reboot WS Proxmox node without downtime]]<br /> * [[Resize VM Disk]]<br /> * [[SRE tools]]<br /> * [[Enroll Mac in Kerberos]]<br /> * [[New Mac Setup]]<br /> * [[Creating a VM on Hetzner]]<br /> * [[Rebooting VM]]<br /> * [[Rebooting Offsite]]<br /> * [[ssh-fingerprints|Verifying SSH fingerprints]]<br /> * [[Removing VM]]<br /> * [[Install a new Disk in Server]]<br /> * [[Setting Up Wildcard Subdomains with SSL on a Debian Application]]<br /> * [[s3 bucket backup|Get credentials to backup S3 bucket to Zombie]]<br /> * [[Hardware Incident Response: Memory Slot Failure on banshee]]<br /> * [[dfz switch setup|DFZ Switch setup]]<br /> * [[Update Zulip Server version]]<br /> * [[update-sentry|Update Sentry]]<br /> * [[iDRAC: Upload a new pem certificate for automatic updates]]<br /> === SLA ===<br /> * [[Response for Backup Service being down for an extended period of time]]<br /> <br /> == Other ==<br /> <br /> * [[stack|Greenfield stack]]<br /> * [[standard tools|Standard Tools]]<br /> * [[list of unfurl debuggers|List of unfurl debuggers]]<br /> * [[Recommended suppliers]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=S3_bucket_backup&diff=638 2025-09-04T14:25:04Z

<p>Vincent: /* Prerequisites */</p> <hr /> <div>== Prerequisites ==<br /> You need to provide Max with these things to enable him to setup backups for the desired S3 storage host<br /> * backup retention policy (How long should backups be retained?)<br /> * estimated backup size (How large do we expect the backups to be?)<br /> * host name (What is the host name of the storage VM we want to backup from?)<br /> <br /> ===Lead Time===<br /> Max indicated minimum lead time for setting up a backup repository and providing credentials is 2 (working) days</div>

Vincent https://docs.delftsolutions.nl/index.php?title=S3_bucket_backup&diff=637 2025-09-04T14:23:03Z

<p>Vincent: /* Prerequisites */</p> <hr /> <div>== Prerequisites ==<br /> - backup retention policy<br /> - How long should backups be retained?<br /> - estimated backup size<br /> - How large do we expect the backups to be?<br /> - host name<br /> - What is the host name of the storage VM we want to backup from?<br /> <br /> Provide these details to Max when asking for credentials to backup to zombie<br /> <br /> ===Lead Time===<br /> Max indicated minimum lead time for setting up a backup repository and providing credentials is 2 (working) days</div>

Vincent https://docs.delftsolutions.nl/index.php?title=S3_bucket_backup&diff=636 2025-09-04T14:22:52Z

<p>Vincent: Created page with &quot;== Prerequisites == - backup retention policy - How long should backups be retained? - estimated backup size - How large do we expect the backups to be? - host name - What is the host name of the storage VM we want to backup from? Provide these details to Max when asking for credentials to backup to zombie ===Lead Time=== Max indicated minimum lead time for setting up a backup repository and providing credentials is 2 (working) days&quot;</p> <hr /> <div>== Prerequisites ==<br /> - backup retention policy<br /> - How long should backups be retained?<br /> - estimated backup size<br /> - How large do we expect the backups to be?<br /> - host name<br /> - What is the host name of the storage VM we want to backup from?<br /> <br /> Provide these details to Max when asking for credentials to backup to zombie<br /> <br /> ===Lead Time===<br /> Max indicated minimum lead time for setting up a backup repository and providing credentials is 2 (working) days</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=635 2025-09-04T14:20:06Z

<p>Vincent: /* SRE */</p> <hr /> <div>== Strategy ==<br /> * [[Flow metrics|Flow metrics]]<br /> * [[12%-time|12%-time]]<br /> <br /> == Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking bonus|Booking bonus]]<br /> * [[booking wages|Booking wages]]<br /> * [[booking quarterly hosting invoice|Booking quarterly hosting invoice]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> * [[invoice approval|Process for approving invoices (/filed receipts)]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Work Process ==<br /> <br /> * [[Definition of done|Definition of Done]]<br /> * [[Incident Handling|Incident Handling]]<br /> * [[SRE Maintenance|SRE Maintenance]]<br /> * [[Release checklist|Release checklist]]<br /> <br /> == Internal Process ==<br /> * [[timetracking|Timetracking process]]<br /> * [[Starting work for a new client]]<br /> * [[12 percent|12% time]]<br /> * [[Annual leave|Annual leave]]<br /> * [[Bonus allocation|Bonus allocation]]<br /> * [[Calamity leave|Calamity leave]]<br /> * [[Overtime|Overtime]]<br /> * [[Retrospectives|Retrospectives]]<br /> * [[Sick leave|Sick leave]]<br /> * [[Training and self-study|Training and Self-Study]]<br /> * [[Daily|Daily]]<br /> <br /> == Projects ==<br /> <br /> * Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]<br /> * [[border update|Process for updating a border]]<br /> * [[border reboot|Reboot border without downtime]]<br /> * [[WS Proxmox node reboot|Reboot WS Proxmox node without downtime]]<br /> * [[Resize VM Disk]]<br /> * [[SRE tools]]<br /> * [[Enroll Mac in Kerberos]]<br /> * [[New Mac Setup]]<br /> * [[Creating a VM on Hetzner]]<br /> * [[Rebooting VM]]<br /> * [[Rebooting Offsite]]<br /> * [[ssh-fingerprints|Verifying SSH fingerprints]]<br /> * [[Removing VM]]<br /> * [[Install a new Disk in Server]]<br /> * [[Setting Up Wildcard Subdomains with SSL on a Debian Application]]<br /> * [[s3 bucket backup|Get credentials to backup S3 bucket to Zombie]]<br /> * [[Hardware Incident Response: Memory Slot Failure on banshee]]<br /> * [[dfz switch setup|DFZ Switch setup]]<br /> === SLA ===<br /> * [[Response for Backup Service being down for an extended period of time]]<br /> <br /> == Other ==<br /> <br /> * [[stack|Greenfield stack]]<br /> * [[standard tools|Standard Tools]]<br /> * [[list of unfurl debuggers|List of unfurl debuggers]]<br /> * [[Recommended suppliers]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Dfz_switch_setup&diff=634 2025-09-03T20:39:51Z

<p>Vincent: </p> <hr /> <div>== Dell PowerConnect 8132 ==<br /> This is currently dfz2<br /> <br /> === Prerequisites ===<br /> * Physicial access to the switch<br /> * Ethernet cable<br /> * Serial to x cable<br /> * Computer with x port and ethernet port<br /> * Host entry in IPA for the switch with the exact hostname<br /> * Ask Max in advance to make time to create a signed certificate from a certificate signing request (last time took multiple hours)<br /> <br /> === Initial setup ===<br /> <br /> &lt;START SERIAL CONNECTION TO SWITCH&gt;<br /> Prefer to use another serial emulator (e.g. minicom) but this is what we know for now<br /> * screen /dev/tty.usbserial-AB87E34V 9600 # /dev/&lt;device&gt; may be different on your machine, 9600 is the baud/data-rate and is default for the switch<br /> * enable<br /> <br /> SKIP NEXT STEP WHEN IN BROKEN STATE<br /> * copy startup-config backup-config <br /> <br /> * configure<br /> * interface vlan 1<br /> * ip address 192.168.0.10 255.255.0.0<br /> * exit<br /> * exit<br /> * show ip interface vlan 1<br /> <br /> &lt;END SERIAL CONNECTION TO SWITCH&gt;<br /> <br /> &lt;START WEBGUI CONFIGURE VLAN ADMIN ON PORT 1&gt;<br /> * connect ethernet cable to switch<br /> * set your local ip address to e.g. 192.168.0.9/16<br /> * navigate to (http://)192.168.0.10<br /> * login<br /> * Switching &gt; VLAN &gt; VLAN Membership<br /> * Add (VLAN ID &lt;ADMIN_VLAN_ID&gt;; VLAN NAME &quot;admin&quot;)<br /> * Add (VLAN ID &lt;DFZ_VLAN_ID&gt;; VLAN NAME &quot;dfz&quot;)<br /> * Detail<br /> * Show VLAN &lt;DFZ_VLAN_ID&gt;-dfz<br /> * Select all ports which should be part of this VLAN<br /> * Click &quot;Apply&quot;<br /> * repeat for VLAN &lt;ADMIN_VLAN_ID&gt;-admin with port 1 (and possibly 2 or more) # Once you hit Apply you will lose connection to the webgui as there is no ip address set for interface vlan &lt;ADMIN_VLAN_ID&gt;<br /> <br /> &lt;END WEBGUI CONFIGURE VLAN ADMIN ON PORT 1&gt;<br /> <br /> &lt;START SERIAL CONNECTION TO SWITCH&gt;<br /> <br /> * enable<br /> * configure<br /> * interface vlan &lt;ADMIN_VLAN_ID&gt;<br /> * ipv6 address &lt;IPV6_ADDRESS&gt;<br /> * ipv6 enable<br /> * exit<br /> * exit<br /> * show ipv6 interface vlan &lt;ADMIN_VLAN_ID&gt;<br /> * configure<br /> * interface vlan 1<br /> * no ip address<br /> * exit<br /> * exit<br /> * show ip interface vlan 1<br /> <br /> # PERSIST CONFIG<br /> * copy running-config startup-config<br /> <br /> === SSL Certificate ===<br /> <br /> * Connect your computer to ethernet port 1 (or any other port on the admin vlan).<br /> * Navigate to switch webinterface.<br /> * Navigate to System &gt; Management Security &gt; HTTPS (Unsure about exact menu headings)<br /> * Here fill in hostname (SAME AS HOST CREATED IN IPA) for the switch as name, country: &quot;NL&quot;, organization-name: &quot;Delft Solutions&quot;, key length: 2048, duration: 365<br /> * Click Generate certificate<br /> * Navigate to System &gt; File management &gt; Upload files<br /> * From this view, using the HTTP method, downloa the relevant certificate and key files<br /> * In your terminal, generate a Certificate Signing Request (CSR) with &lt;code&gt;openssl x509 -in sslt_cert1.pem -signkey sslt_key1.pem -x509toreq -out domain.csr&lt;/code&gt;<br /> * Give Max the resulting CSR and ask him to create the signed certificate for the host<br /> * When certificate has been generated successfully, download it from IPA<br /> * Establish serial connection to switch<br /> * &lt;code&gt;enable&lt;/code&gt;<br /> * &lt;code&gt;configure&lt;/code&gt;<br /> * &lt;code&gt;crypto certificate &lt;CERT_NUMBER&gt; import&lt;/code&gt;<br /> * paste signed certificate<br /> * In webinterface, verify the newly signed certificate is now present<br /> * In webinterface, enable HTTPS admin mode<br /> * Navigate to https://&lt;SWITCH_URL&gt; in order to confirm HTTPS is enabled and the certificate is valid<br /> * login<br /> * save configuration<br /> <br /> ==== When overwriting certs and/or keys ====<br /> <br /> Generated Key+CSR with OpenSSL in RSA 2048Bit SHA-256.The naming of the key on the switch is sslt_key1.pem and the cert is sslt_cert1.pem. Copy these files to flash:// and they override the existing ones, reload the website and it's working.</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Dfz_switch_setup&diff=633 2025-09-03T16:05:46Z

<p>Vincent: Created page with &quot;== Dell PowerConnect 8132 == This is currently dfz2 === Prerequisites === * Physicial access to the switch * Ethernet cable * Serial to x cable * Computer with x port and ethernet port * Host entry in IPA for the switch with the exact hostname * Ask Max in advance to make time to create a signed certificate from a certificate signing request (last time took multiple hours) === Initial setup === &lt;START SERIAL CONNECTION TO SWITCH&gt; Prefer to use another serial emulator...&quot;</p> <hr /> <div>== Dell PowerConnect 8132 ==<br /> This is currently dfz2<br /> <br /> === Prerequisites ===<br /> * Physicial access to the switch<br /> * Ethernet cable<br /> * Serial to x cable<br /> * Computer with x port and ethernet port<br /> * Host entry in IPA for the switch with the exact hostname<br /> * Ask Max in advance to make time to create a signed certificate from a certificate signing request (last time took multiple hours)<br /> <br /> === Initial setup ===<br /> <br /> &lt;START SERIAL CONNECTION TO SWITCH&gt;<br /> Prefer to use another serial emulator (e.g. minicom) but this is what we know for now<br /> * screen /dev/tty.usbserial-AB87E34V 9600 # /dev/&lt;device&gt; may be different on your machine, 9600 is the baud/data-rate and is default for the switch<br /> * enable<br /> <br /> SKIP NEXT STEP WHEN IN BROKEN STATE<br /> * copy startup-config backup-config <br /> <br /> * configure<br /> * interface vlan 1<br /> * ip address 192.168.0.10 255.255.0.0<br /> * exit<br /> * exit<br /> * show ip interface vlan 1<br /> <br /> &lt;END SERIAL CONNECTION TO SWITCH&gt;<br /> <br /> &lt;START WEBGUI CONFIGURE VLAN ADMIN ON PORT 1&gt;<br /> * connect ethernet cable to switch<br /> * set your local ip address to e.g. 192.168.0.9/16<br /> * navigate to (http://)192.168.0.10<br /> * login<br /> * Switching &gt; VLAN &gt; VLAN Membership<br /> * Add (VLAN ID &lt;ADMIN_VLAN_ID&gt;; VLAN NAME &quot;admin&quot;)<br /> * Add (VLAN ID &lt;DFZ_VLAN_ID&gt;; VLAN NAME &quot;dfz&quot;)<br /> * Detail<br /> * Show VLAN &lt;DFZ_VLAN_ID&gt;-dfz<br /> * Select all ports which should be part of this VLAN<br /> * Click &quot;Apply&quot;<br /> * repeat for VLAN &lt;ADMIN_VLAN_ID&gt;-admin with port 1 (and possibly 2 or more) # Once you hit Apply you will lose connection to the webgui as there is no ip address set for interface vlan &lt;ADMIN_VLAN_ID&gt;<br /> <br /> &lt;END WEBGUI CONFIGURE VLAN ADMIN ON PORT 1&gt;<br /> <br /> &lt;START SERIAL CONNECTION TO SWITCH&gt;<br /> <br /> * enable<br /> * configure<br /> * interface vlan &lt;ADMIN_VLAN_ID&gt;<br /> * ipv6 address &lt;IPV6_ADDRESS&gt;<br /> * ipv6 enable<br /> * exit<br /> * exit<br /> * show ipv6 interface vlan &lt;ADMIN_VLAN_ID&gt;<br /> * configure<br /> * interface vlan 1<br /> * no ip address<br /> * exit<br /> * exit<br /> * show ip interface vlan 1<br /> <br /> # PERSIST CONFIG<br /> * copy running-config startup-config<br /> <br /> === SSL Certificate ===<br /> <br /> * Connect your computer to ethernet port 1 (or any other port on the admin vlan).<br /> * Navigate to switch webinterface.<br /> * Navigate to System &gt; Management Security &gt; HTTPS (Unsure about exact menu headings)<br /> * Here fill in hostname (SAME AS HOST CREATED IN IPA) for the switch as name, country: &quot;NL&quot;, organization-name: &quot;Delft Solutions&quot;, key length: 2048, duration: 365<br /> * Click Generate certificate<br /> * Navigate to System &gt; File management &gt; Upload files<br /> * From this view, using the HTTP method, downloa the relevant certificate and key files<br /> * In your terminal, generate a Certificate Signing Request (CSR) with &lt;code&gt;openssl x509 -in sslt_cert1.pem -signkey sslt_key1.pem -x509toreq -out domain.csr&lt;/code&gt;<br /> * Give Max the resulting CSR and ask him to create the signed certificate for the host<br /> * When certificate has been generated successfully, download it from IPA<br /> * Establish serial connection to switch<br /> * &lt;code&gt;enable&lt;/code&gt;<br /> * &lt;code&gt;configure&lt;/code&gt;<br /> * &lt;code&gt;crypto certificate &lt;CERT_NUMBER&gt; import&lt;/code&gt;<br /> * paste signed certificate<br /> * In webinterface, verify the newly signed certificate is now present<br /> * In webinterface, enable HTTPS admin mode<br /> * Navigate to https://&lt;SWITCH_URL&gt; in order to confirm HTTPS is enabled and the certificate is valid<br /> * login<br /> * save configuration</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=632 2025-09-03T15:22:21Z

<p>Vincent: /* SRE */</p> <hr /> <div>== Strategy ==<br /> * [[Flow metrics|Flow metrics]]<br /> * [[12%-time|12%-time]]<br /> <br /> == Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking bonus|Booking bonus]]<br /> * [[booking wages|Booking wages]]<br /> * [[booking quarterly hosting invoice|Booking quarterly hosting invoice]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> * [[invoice approval|Process for approving invoices (/filed receipts)]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Work Process ==<br /> <br /> * [[Definition of done|Definition of Done]]<br /> * [[Incident Handling|Incident Handling]]<br /> * [[SRE Maintenance|SRE Maintenance]]<br /> * [[Release checklist|Release checklist]]<br /> <br /> == Internal Process ==<br /> * [[timetracking|Timetracking process]]<br /> * [[Starting work for a new client]]<br /> * [[12 percent|12% time]]<br /> * [[Annual leave|Annual leave]]<br /> * [[Bonus allocation|Bonus allocation]]<br /> * [[Calamity leave|Calamity leave]]<br /> * [[Overtime|Overtime]]<br /> * [[Retrospectives|Retrospectives]]<br /> * [[Sick leave|Sick leave]]<br /> * [[Training and self-study|Training and Self-Study]]<br /> * [[Daily|Daily]]<br /> <br /> == Projects ==<br /> <br /> * Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]<br /> * [[border update|Process for updating a border]]<br /> * [[border reboot|Reboot border without downtime]]<br /> * [[WS Proxmox node reboot|Reboot WS Proxmox node without downtime]]<br /> * [[Resize VM Disk]]<br /> * [[SRE tools]]<br /> * [[Enroll Mac in Kerberos]]<br /> * [[New Mac Setup]]<br /> * [[Creating a VM on Hetzner]]<br /> * [[Rebooting VM]]<br /> * [[Rebooting Offsite]]<br /> * [[ssh-fingerprints|Verifying SSH fingerprints]]<br /> * [[Removing VM]]<br /> * [[Install a new Disk in Server]]<br /> * [[Setting Up Wildcard Subdomains with SSL on a Debian Application]]<br /> * [[Hardware Incident Response: Memory Slot Failure on banshee]]<br /> * [[dfz switch setup|DFZ Switch setup]]<br /> === SLA ===<br /> * [[Response for Backup Service being down for an extended period of time]]<br /> <br /> == Other ==<br /> <br /> * [[stack|Greenfield stack]]<br /> * [[standard tools|Standard Tools]]<br /> * [[list of unfurl debuggers|List of unfurl debuggers]]<br /> * [[Recommended suppliers]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_wages&diff=631 2025-08-06T14:20:04Z

<p>Vincent: </p> <hr /> <div>== Wage slips ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken (English: Financial -&gt; Entries &amp; G/L Accounts -&gt; Entries -&gt; Create)<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (wage slip)<br /> # Set `Supplier` to the person this wage slip meant for<br /> # Beschijving: Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}<br /> # Ensure `Payment condition` is set to `M - Einde volgende maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the wage slip pertains to<br /> # Totaalbedrag: Set to '''Totaal netto''' from the wage slip<br /> # Line items:<br /> ## From the wage slip's '''Bruto &gt; Salaris''' add the value of it as '''Bruto loon (4000)''', with description 'Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Bruto &gt; Bonus (BT)''' if present, add the value of it as '''Te betalen bonussen (1790)''' with description 'Salaris bonus {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Loonheffing''' add the value of it as a negative amount as '''af te dragen loonheffing (1700)''', with description 'Salaris LH {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Netto &gt; Onkostenvergoeding''' if present, add the value of it as '''Kosten nettovergoedingen'''<br /> <br /> == Wage taxes ==<br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (LH/'Loonaangifte_Bedrijf_Overzicht_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Belastingdienst`<br /> # Beschrijving: Enter the value for ''LHnummer en volgnummer'' from the document<br /> # Ensure `Payment Condition` is set to `D - Deze maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the taxes should be paid in, if the 'send' date on the document is not of the same month. Otherwise, just set the 'send' date<br /> # Set `Total amount` to the value of `Totaal Generaal` from the document<br /> # Line items:<br /> ## From the document's '''Loonbelasting / premie volksverzekering''' add the section's total value as '''Af te dragen loonheffing (1700)''' with description `Loonbelasting / premie volksverzekering {YEAR}-{MONTH}`<br /> ## From the document's '''Premies''' add the section's total value as '''Kosten sociale premies werkgever (4041)''' with description `Premies {YEAR}-{MONTH}`<br /> <br /> == Pension ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (JP/'Journaalposten_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Bright Pensions N.V.`<br /> # Beschrijving: Pensioen {YEAR}-{MONTH}-M<br /> # Ensure `Payment condition` is set to `IN - Incasso`<br /> # Ensure `Invoice date` is set to the the '16th' of the month of the period over which the document documents the pension payments. (Look at 'Periodes' for this)<br /> # Totaalbedrag: Set to the value of '''Pensioenafdracht WG en WN''' on the document<br /> # Line items:<br /> ## For each person who received pension payment: '''Pensioenen (4011)''' with description `Pensioen {YEAR}-{MONTH}-M {NAME}` and with the correct value.<br /> <br /> == Reconciliation (after payment) ==<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Overzichten &gt; Kaarten (In English: Financial &gt; Entries &amp; G/L Accounts &gt; Reports &gt; Transactions)<br /> # Search for '''Af te dragen loonheffing (1700)'''. Ensure the relevant `Financial year` is selected.<br /> # First, only mark (not actually match) the wage slips together with the IRS slip for wage taxes. The difference at the bottom (e.g. 0.16 EUR) needs to be added to the wage tax document.<br /> ## For line item '''Af te dragen loonheffing (1700)''' add the difference to the current value (0.16 EUR in this example)<br /> ## Create line item '''Rekenverschillen (9200)''' with description {ENTRY_DESCRIPTION} {YEAR}-{MONTH} and the value in negative (-0.16 EUR in this example)<br /> ## Mark the wage slips together with the IRS slip for wage taxes again. The difference should now be 0.<br /> # Select `Afletteren` (`Match`) at the top of the screen to match the entries.<br /> <br /> == Reconciliation of the payment itself ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L account is set to `1671 - Te betalen lonen`, and the account is set to `1 - Belastingdienst`.<br /> # Select `Match` and select the matching entry (Previously created in the `Wage Taxes` section).<br /> <br /> == Reconciliation of the pension payments ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L is set to `1671 - Te betalen lonen`, and the account is set to `47 - Bring Pensions N.V.` for the three pension payments.<br /> # Click 'Match' on any of the pension payments<br /> # In the modal, check the checkbox for the other two pension payments, and the correct pension document entry (The one created earlier in the `Pension` section). Finally, click `Enter`.<br /> <br /> == Preparing wage payments ==<br /> # Create a payment scheduled on the correct date (15th of the month) for 12:00 (Midday), for each wage slip added, with the description `Salaris periode {YEAR}-{MONTH}-M {NAME}`</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_wages&diff=630 2025-08-06T14:12:38Z

<p>Vincent: </p> <hr /> <div>== Wage slips ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken (English: Financial -&gt; Entries &amp; G/L Accounts -&gt; Entries -&gt; Create)<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (wage slip)<br /> # Set `Supplier` to the person this wage slip meant for<br /> # Beschijving: Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}<br /> # Ensure `Payment condition` is set to `M - Einde volgende maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the wage slip pertains to<br /> # Totaalbedrag: Set to '''Totaal netto''' from the wage slip<br /> # Line items:<br /> ## From the wage slip's '''Bruto &gt; Salaris''' add the value of it as '''Bruto loon (4000)''', with description 'Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Bruto &gt; Bonus (BT)''' if present, add the value of it as '''Te betalen bonussen (1790)''' with description 'Salaris bonus {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Loonheffing''' add the value of it as a negative amount as '''af te dragen loonheffing (1700)''', with description 'Salaris LH {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Netto &gt; Onkostenvergoeding''' if present, add the value of it as '''Kosten nettovergoedingen'''<br /> <br /> == Wage taxes ==<br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (LH/'Loonaangifte_Bedrijf_Overzicht_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Belastingdienst`<br /> # Beschrijving: Enter the value for ''LHnummer en volgnummer'' from the document<br /> # Ensure `Payment Condition` is set to `D - Deze maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the taxes should be paid in, if the 'send' date on the document is not of the same month. Otherwise, just set the 'send' date<br /> # Set `Total amount` to the value of `Totaal Generaal` from the document<br /> # Line items:<br /> ## From the document's '''Loonbelasting / premie volksverzekering''' add the section's total value as '''Af te dragen loonheffing (1700)''' with description `Loonbelasting / premie volksverzekering {YEAR}-{MONTH}`<br /> ## From the document's '''Premies''' add the section's total value as '''Kosten sociale premies werkgever (4041)''' with description `Premies {YEAR}-{MONTH}`<br /> <br /> == Pension ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (JP/'Journaalposten_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Bright Pensions N.V.`<br /> # Beschrijving: Pensioen {YEAR}-{MONTH}-M<br /> # Ensure `Payment condition` is set to `IN - Incasso`<br /> # Ensure `Invoice date` is set to the the '16th' of the month of the period over which the document documents the pension payments. (Look at 'Periodes' for this)<br /> # Totaalbedrag: Set to the value of '''Pensioenafdracht WG en WN''' on the document<br /> # Line items:<br /> ## For each person who received pension payment: '''Pensioenen (4011)''' with description `Pensioen {YEAR}-{MONTH}-M {NAME}` and with the correct value.<br /> <br /> == Reconciliation (after payment) ==<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Overzichten &gt; Kaarten (In English: Financial &gt; Entries &amp; G/L Accounts &gt; Reports &gt; Transactions)<br /> # Search for '''Af te dragen loonheffing (1700)'''. Ensure the relevant `Financial year` is selected.<br /> # First, only mark (not actually match) the wage slips together with the IRS slip for wage taxes. The difference at the bottom (e.g. 0.16 EUR) needs to be added to the wage tax document.<br /> ## For line item '''Af te dragen loonheffing (1700)''' add the difference to the current value (0.16 EUR in this example)<br /> ## Create line item '''Rekenverschillen (9200)''' with description {ENTRY_DESCRIPTION} {YEAR}-{MONTH} and the value in negative (-0.16 EUR in this example)<br /> ## Mark the wage slips together with the IRS slip for wage taxes again. The difference should now be 0.<br /> # Select `Match` at the top of the screen to match the entries.<br /> <br /> == Reconciliation of the payment itself ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L account is set to `1671 - Te betalen lonen`, and the account is set to `1 - Belastingdienst`.<br /> # Select `Match` and select the matching entry (Previously created in the `Wage Taxes` section).<br /> <br /> == Reconciliation of the pension payments ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L is set to `1671 - Te betalen lonen`, and the account is set to `47 - Bring Pensions N.V.` for the three pension payments.<br /> # Click 'Match' on any of the pension payments<br /> # In the modal, check the checkbox for the other two pension payments, and the correct pension document entry (The one created earlier in the `Pension` section). Finally, click `Enter`.<br /> <br /> == Preparing wage payments ==<br /> # Create a payment scheduled on the correct date (15th of the month) for 12:00 (Midday), for each wage slip added, with the description `Salaris periode {YEAR}-{MONTH}-M {NAME}`</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_wages&diff=629 2025-08-06T13:30:28Z

<p>Vincent: </p> <hr /> <div>== Wage slips ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken (English: Financial -&gt; Entries &amp; G/L Accounts -&gt; Entries -&gt; Create)<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (wage slip)<br /> # Set `Supplier` to the person this wage slip meant for<br /> # Beschijving: Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}<br /> # Ensure `Payment condition` is set to `M - Einde volgende maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the wage slip pertains to<br /> # Totaalbedrag: Set to '''Totaal netto''' from the wage slip<br /> # Line items:<br /> ## From the wage slip's '''Bruto &gt; Salaris''' add the value of it as '''Bruto loon (4000)''', with description 'Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Bruto &gt; Bonus (BT)''' if present, add the value of it as '''Te betalen bonussen (1790)''' with description 'Salaris bonus {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Loonheffing''' add the value of it as a negative amount as '''af te dragen loonheffing (1700)''', with description 'Salaris LH {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Netto &gt; Onkostenvergoeding''' if present, add the value of it as '''Kosten nettovergoedingen'''<br /> <br /> == Wage taxes ==<br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (LH/'Loonaangifte_Bedrijf_Overzicht_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Belastingdienst`<br /> # Beschrijving: Enter the value for ''LHnummer en volgnummer'' from the document<br /> # Ensure `Payment Condition` is set to `D - Deze maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the taxes should be paid in, if the 'send' date on the document is not of the same month. Otherwise, just set the 'send' date<br /> # Set `Total amount` to the value of `Totaal Generaal` from the document<br /> # Line items:<br /> ## From the document's '''Loonbelasting / premie volksverzekering''' add the section's total value as '''Af te dragen loonheffing (1700)''' with description `Loonbelasting / premie volksverzekering {YEAR}-{MONTH}`<br /> ## From the document's '''Premies''' add the section's total value as '''Kosten sociale premies werkgever (4041)''' with description `Premies {YEAR}-{MONTH}`<br /> <br /> == Pension ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (JP/'Journaalposten_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Bright Pensions N.V.`<br /> # Beschrijving: Pensioen {YEAR}-{MONTH}-M<br /> # Ensure `Payment condition` is set to `IN - Incasso`<br /> # Ensure `Invoice date` is set to the the '16th' of the month of the period over which the document documents the pension payments. (Look at 'Periodes' for this)<br /> # Totaalbedrag: Set to the value of '''Pensioenafdracht WG en WN''' on the document<br /> # Line items:<br /> ## For each person who received pension payment: '''Pensioenen (4011)''' with description `Pensioen {YEAR}-{MONTH}-M {NAME}` and with the correct value (At the moment, 1/3 of the total amount per person).<br /> <br /> == Reconciliation (after payment) ==<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Overzichten &gt; Kaarten (In English: Financial &gt; Entries &amp; G/L Accounts &gt; Reports &gt; Transactions)<br /> # Search for '''Af te dragen loonheffing (1700)'''. Ensure the relevant `Financial year` is selected.<br /> # First, only mark (not actually match) the wage slips together with the IRS slip for wage taxes. The difference at the bottom (e.g. 0.16 EUR) needs to be added to the wage tax document.<br /> ## For line item '''Af te dragen loonheffing (1700)''' add the difference to the current value (0.16 EUR in this example)<br /> ## Create line item '''Rekenverschillen (9200)''' with description {ENTRY_DESCRIPTION} {YEAR}-{MONTH} and the value in negative (-0.16 EUR in this example)<br /> ## Mark the wage slips together with the IRS slip for wage taxes again. The difference should now be 0.<br /> # Select `Match` at the top of the screen to match the entries.<br /> <br /> == Reconciliation of the payment itself ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L account is set to `1671 - Te betalen lonen`, and the account is set to `1 - Belastingdienst`.<br /> # Select `Match` and select the matching entry (Previously created in the `Wage Taxes` section).<br /> <br /> == Reconciliation of the pension payments ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L is set to `1671 - Te betalen lonen`, and the account is set to `47 - Bring Pensions N.V.` for the three pension payments.<br /> # Click 'Match' on any of the pension payments<br /> # In the modal, check the checkbox for the other two pension payments, and the correct pension document entry (The one created earlier in the `Pension` section). Finally, click `Enter`.<br /> <br /> == Preparing wage payments ==<br /> # Create a payment scheduled on the correct date (15th of the month) for 12:00 (Midday), for each wage slip added, with the description `Salaris periode {YEAR}-{MONTH}-M {NAME}`</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_wages&diff=628 2025-08-06T13:24:14Z

<p>Vincent: </p> <hr /> <div>== Wage slips ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken (English: Financial -&gt; Entries &amp; G/L Accounts -&gt; Entries -&gt; Create)<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (wage slip)<br /> # Set `Supplier` to the person this wage slip meant for<br /> # Beschijving: Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}<br /> # Ensure `Payment condition` is set to `M - Einde volgende maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the wage slip pertains to<br /> # Totaalbedrag: Set to '''Totaal netto''' from the wage slip<br /> # Line items:<br /> ## From the wage slip's '''Bruto &gt; Salaris''' add the value of it as '''Bruto loon (4000)''', with description 'Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Bruto &gt; Bonus (BT)''' if present, add the value of it as '''Te betalen bonussen (1790)''' with description 'Salaris bonus {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Loonheffing''' add the value of it as a negative amount as '''af te dragen loonheffing (1700)''', with description 'Salaris LH {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}'<br /> ## From the wage slip's '''Netto &gt; Onkostenvergoeding''' if present, add the value of it as '''Kosten nettovergoedingen'''<br /> <br /> == Wage taxes ==<br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (LH/'Loonaangifte_Bedrijf_Overzicht_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Belastingdienst`<br /> # Beschrijving: Enter the value for ''LHnummer en volgnummer'' from the document<br /> # Ensure `Payment Condition` is set to `D - Deze maand`<br /> # Ensure `Invoice date` is set to the beginning of the month the taxes pertain to, if the 'send' date on the document is not of the same month. Otherwise, just set the 'send' date<br /> # Set `Total amount` to the value of `Totaal Generaal` from the document<br /> # Line items:<br /> ## From the document's '''Loonbelasting / premie volksverzekering''' add the section's total value as '''Af te dragen loonheffing (1700)''' with description `Loonbelasting / premie volksverzekering {YEAR}-{MONTH}`<br /> ## From the document's '''Premies''' add the section's total value as '''Kosten sociale premies werkgever (4041)''' with description `Premies {YEAR}-{MONTH}`<br /> <br /> == Pension ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (JP/'Journaalposten_Delft_Solutions_BV_*.pdf)<br /> # Set `Supplier` to `Bright Pensions N.V.`<br /> # Beschrijving: Pensioen {YEAR}-{MONTH}-M<br /> # Ensure `Payment condition` is set to `IN - Incasso`<br /> # Ensure `Invoice date` is set to the the '16th' of the month of the period over which the document documents the pension payments. (Look at 'Periodes' for this)<br /> # Totaalbedrag: Set to the value of '''Pensioenafdracht WG en WN''' on the document<br /> # Line items:<br /> ## For each person who received pension payment: '''Pensioenen (4011)''' with description `Pensioen {YEAR}-{MONTH}-M {NAME}` and with the correct value (At the moment, 1/3 of the total amount per person).<br /> <br /> == Reconciliation (after payment) ==<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Overzichten &gt; Kaarten (In English: Financial &gt; Entries &amp; G/L Accounts &gt; Reports &gt; Transactions)<br /> # Search for '''Af te dragen loonheffing (1700)'''. Ensure the relevant `Financial year` is selected.<br /> # First, only mark (not actually match) the wage slips together with the IRS slip for wage taxes. The difference at the bottom (e.g. 0.16 EUR) needs to be added to the wage tax document.<br /> ## For line item '''Af te dragen loonheffing (1700)''' add the difference to the current value (0.16 EUR in this example)<br /> ## Create line item '''Rekenverschillen (9200)''' with description {ENTRY_DESCRIPTION} {YEAR}-{MONTH} and the value in negative (-0.16 EUR in this example)<br /> ## Mark the wage slips together with the IRS slip for wage taxes again. The difference should now be 0.<br /> # Select `Match` at the top of the screen to match the entries.<br /> <br /> == Reconciliation of the payment itself ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L account is set to `1671 - Te betalen lonen`, and the account is set to `1 - Belastingdienst`.<br /> # Select `Match` and select the matching entry (Previously created in the `Wage Taxes` section).<br /> <br /> == Reconciliation of the pension payments ==<br /> # Go to Financial &gt; Banking &amp; Cash &gt; Statements &gt; To be completed and search for `to be completed` statements.<br /> # Ensure the G/L is set to `1671 - Te betalen lonen`, and the account is set to `47 - Bring Pensions N.V.` for the three pension payments.<br /> # Click 'Match' on any of the pension payments<br /> # In the modal, check the checkbox for the other two pension payments, and the correct pension document entry (The one created earlier in the `Pension` section). Finally, click `Enter`.<br /> <br /> == Preparing wage payments ==<br /> # Create a payment scheduled on the correct date (15th of the month) for 12:00 (Midday), for each wage slip added, with the description `Salaris periode {YEAR}-{MONTH}-M {NAME}`</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Incident_Handling&diff=622 2025-06-24T08:47:53Z

<p>Vincent: </p> <hr /> <div>= Checklist =<br /> This checklist is a shorter, imperative version of [[Incident Handling#Full_procedure|the longer procedure below]]. You're encouraged to read the [[Incident Handling#Full_procedure|full procedure]] at least once to improve your understanding of the core material.<br /> <br /> === Critical Incidents ===<br /> Critical incidents must be resolved within 16 hours. <br /> <br /> # Acknowledge trigger in Zabbix.<br /> # Check if incident is still ongoing.<br /> # If ongoing and clients are potentially affected, notify the affected clients via Slack (when done, communicate this internally).<br /> # Document all actions taken in Zulip topic.<br /> # Create plan of action.<br /> # Execute plan and document results in Zabbix thread. <br /> # If unresolved, create new plan.<br /> # When resolved:<br /> ## Verify trigger is no longer firing.<br /> ## Decide on when to notify affected clients (that you have notified of the incident) the incident has been resolved, and communicate this internally<br /> ## Mark Zulip topic as resolved if no other incidents for host.<br /> ## Check for related triggers and resolve them.<br /> <br /> Common issues that have occurred previously, and ''could'' occur again:<br /> * SSH down: Check MaxStartups throttling, apply custom SSH config<br /> * No backup: Verify backup process is running, check devteam email<br /> * HTTPS down on Sunday: this can be due to Gitlab updates<br /> <br /> === Non-Critical Incidents ===<br /> Non-critical incidents must be acknowledged within 9 hours and resolved within 1 week.<br /> <br /> # Acknowledge in Zabbix thread<br /> # Check metrics sheet for existing milestone<br /> ## If a milestone exists:<br /> ### Add Lynx project ID to Zulip topic<br /> ### Add 🔁 emoji if ID already reported<br /> ## If no milestone exists:<br /> ### Add to metrics sheet<br /> ### Create Lynx project (priority 99, then 20 after estimation)<br /> ### Create Kimai activity<br /> ### Document IDs in Zulip topic<br /> <br /> === Informational Incidents ===<br /> Informational incidents must be acknowledged within 72 hours.<br /> <br /> # Acknowledge in Zabbix<br /> # Verify issue<br /> # Take action if needed<br /> <br /> === External Reports ===<br /> <br /> # Acknowledge receipt<br /> # Classify report as critical, non-critical or informational. <br /> # Create a Zulip topic in SRE # Critical, SRE ## Non-critical or SRE ### Informational (depending on classification) and add sufficient details. <br /> # Proceed with checklist above for the type of incident.<br /> <br /> = Full procedure =<br /> <br /> == General Rules ==<br /> <br /> # When an incident is in progress, and person A is handling it, then all incidents in area X, are handled by person A, rather than the FR. Unless working day ends. Person A should communicate clearly to FR when their day is over.<br /> # FR always has the last word on what solution to apply for resolving an incident.<br /> <br /> == Zulip migration ==<br /> Due to a migration to Zulip, the integration as was available on Mattermost is not available yet on Zulip. This leads to the following process changes:<br /> * Acknowlegements and triggers resolving are not posted to Zulip by Zabbix<br /> * Triggers are grouped in a topic on Zulip per host<br /> * When an incident has been fully resolved, mark the topic as resolved, when any other incidents reported for the host are resolved<br /> * There's no `?ongoing`, instead for now we can track open incidents by checking for unresolved topics<br /> * The posting of incidents is less smart (only posting when not posted yet), so in order to prevent an incident from not being reported due to network issues or the likes, a message is posted after an inteval (8 hours for non-critical and lower, 1 hour for critical and above) while the incident has not been acknowleged.<br /> * Incidents can be manually tracked by creating a topic by hand and reporting the problem.<br /> * There is no automatic gitlab issue creation or syncing anymore.<br /> <br /> Finally, where this process says to do something on Mattermost, you should now do so on Zulip. The updates in the process chapters themselves are WIP.<br /> <br /> == Critical incidents ==<br /> '''Critical incidents are resolved within 16 hours.'''<br /> <br /> As first responder you take on the responsiblity of seeing an incident resolved. This does not mean that you are the person required to do all the work. You can attempt to involve others to help you (often referred to as escalating the incident), but since other are not on-call, they are not obliged to help you, especially outside of normal working hours.<br /> Involving multiple people can quickly be required if multiple critical incidents with different causes occur simultaneously. In that case, the First Responder usually takes on a more information management role and steers those that are brought on into resolving the issues. (Example: if a server crashes, several critical triggers can fire, but the underlying cause can quite quickly be determined to be a single issue, the crashed server. So you wouldn't need to call in people to manage each incident. But a client's service being down in one cluster while in a different cluster a different VM no longer boots is likely to be to different issues, so in order to resolve them on time you'd want to call in help to resolve the incident in time).<br /> <br /> === Process ===<br /> The general process is made up of the following steps. Each step has additional information on how to handle/execute them in the sections below.<br /> # Take responsibility for seeing the incident resolved<br /> # Determine if incident is still ongoing<br /> # If ongoing: Communicate to affected clients that the issue is being investigated<br /> # Communicate plan/next steps (even if that is gathering information)<br /> # Communicate findings/results of executed plan, go back to previous step if not resolved<br /> # Resolve incident + cleanup<br /> <br /> During working on an incident it is expected that all communication is done in the incident's thread. This means all information to a problem can be found in a clear a predictable place. Sometimes an incident can be resolved by work done in another incident. In that case, it is required to post a link to that thread in the incident's thread with the comment that the resolution is done in that thread.<br /> <br /> ==== Acknowledge the incident on Zabbix ====<br /> The first step is to take responsibility for seeing the incident resolved by acknowledging the incident on Zabbix. Simply acknowledging the trigger suffices. It is however entirely possible that multiple critical incidents are firing at the same time. This can be a coincidence, or can be because of a share cause of failure. For example, a server crashing will cause server VMs to reboot, or the router having an connectivity issue will lead to most other VMs having connectivity issues as well. If there are multiple critical incidents, it is advised to quickly observe what's ongoing, Zabbix is the best source of firing triggers for this, and pick the incident that is likely the root cause to <br /> <br /> * Acknowledging an incident on Zabbix will stop Zabbix from calling the First Responder to notify them of the ongoing incident. And stops Zabbix from posting reminders on Zulip.<br /> <br /> ==== Determine if incident is still ongoing ====<br /> The next step is to check if the reported problem is still ongoing. Depending on the observations made here your process to follow and steps needed to resolve the incident can change. There are three options:<br /> # The trigger resolved itself and the problem cannot be observed. Example: HTTPS is down for a site, but the FR can access the site through HTTPS without incident.<br /> # The trigger resolved itself and the problem can still be observed.<br /> # The trigger is still firing but the problem cannot be observed: Our triggers might not be perfect, so it could be that something else is causing it to fire. A simple example would be that Zabbix reports that the the DNS for a site can't be resolved, but in reality there's a bug in the script we wrote that checks if the DNS resolves and the DNS resolves fine. Final note: keep in mind that an 'it works on my machine' does not necessarily mean it works for most other people, so depening on the trigger you need to do some evaluations if your tests suffice. <br /> <br /> In order to make sure you are actually trying to observe the same thing as the trigger is looking for, make sure to check the trigger definition and the current data of the associated item(s). Some triggers might fire if one of multiple conditions is met (Such as a trigger that monitors the ping response time firing if the value exceeds a certain threshold, or if no data for a certain period of time was observed).<br /> <br /> Make sure to report your findings in the incident's thread. It's advised to post a screenshot of the relevant item(s) and your own observations. (Continuing the ping example, you would post a screenshot of the relevant values, state your conclusion why the trigger is firing, and your own observations/pings)<br /> <br /> ==== Communicate to affected clients ====<br /> If the incident is still ongoing and the service is down, we need to communicate to affected clients that we are aware of the problem and that we are investigating it. This is because critical incident usually mean the service is down, something the clients can notice/are affected by, so we to be transparent that something is going on. There are some additional notes to this though:<br /> * If an incident has already resolved itself and the problem is no longer observable, we don't communicate anything. Doing so might only cause confusion, and since the client has not reported any issues, they have not had a noticeable problem with it themselves.<br /> * Although a critical incident generally means that the client service is down or experiencing reduced service, not all critical incidents are of that nature. Some are more administrative, or are only an issue for Delft Solutions itself. As of writing I don't have an exhaustive list, but here is those I can think of:<br /> ** SSH Service is down: We don't have any clients that SSH into their services, so it's generally not a problem. But SSH is mostly used for SRE maintenance and publishing new builds. The SRE maintenance is an internal problem, so no need to communicate to the client. The publishing is done to Kaboom, preventing new builds from being published, and the two SM VMs.<br /> ** No backup for x days: Clients don't notice it if a backup is running late, so no need to communicate with clients. Just need to make sure the backup gets completed<br /> ** SSL certificate is expiring in &lt; 24 hours: This is a bit dependent on how soon this incident is being handled, but if it handled quickly, the certificate never actually expired, and there has not been any disruption to the client's service, so no need for communicating about it.<br /> * Determining which clients are being affected can be done by looking at the host's DNS in the trigger, and/or looking up the VM in Proxmox and checking the tags of the VMs for client names. In the case that this issue is causing multiple other critical triggers to fire, you would have to check for which clients are affected by those incidents.<br /> * Communicating to DS about ongoing incidents is usually assumed to be automatically have been done by the fact that the incident was reported on Zulip.<br /> <br /> As always, report the decisions taken and actions made in the incident thread. (e.g.: I've sent a message in the Slack to let Kaboom know that we aware of problem x, and that we are investigating it)<br /> <br /> ==== Communicate plan/next steps + Communicate findings/results of executed plan ====<br /> This is the main part of handling an incident. There are several actions you can take in these steps, but at the basis they consist of sharing your next steps, performing those, and reporting the results. The reason all this needs to be reported is to ensure that all known information about a problem is logged, making it easier for someone else to be onboarded into the issue, for later reference if a similar issue is encountered, and even for use during the incident itself in case an older configuration needs to be referenced after you changed it.<br /> The objective from these steps is determining what is actually wrong and how to resolve it. Depending on the observations made earlier on whether the incident is still ongoing and is (still) observable your investigation can go into different directions. (e.g. Find the underlying cause for a trigger, or determining why the trigger is firing while it likely shouldn't, and then how to resolve that underlying cause or how to update the trigger to work better)<br /> <br /> There are three main types of steps defined, but you are not limited to these:<br /> # Hypothesis: If you have an idea what could be causing it, you would state your hypothesis and your next step would be to prove that hypothesis. For example, for an incident 'SSH service is down on X' your hypothesis could be that this is due to 'MaxStartups' throttling, which can be proven by 'grep'ing journalctl for that, and compare the start and end times of throttling with the timestamps of the item reporting the status of the SSH service.<br /> # Information gathering: Sometimes it just helps to get some facts about the situation collected. What is usefull information that is relevant depends on the triggers, but some examples are: The syslog/journalctl of the host from around the time of the incident (it can contain a reference to the an underlying problem in various levels of explicitness), the ping response from several hosts on the route to a host or a traceroute (this helps with networking issues). The gathered information is usually intended to help you come up with an hypothesis on what's wrong.<br /> # Investigative: The most rigorous of process. The full process is described here originally [https://docs.google.com/document/d/1AQYJM1Q9l2Tyk6zfCVaQ2aEq-dpbfUH5okE88bpKkhw/edit#heading=h.5fq2skijqbdc Drive - Final Coundown - General Investigative Process]. To summarize, when you don't know why something is failing, and/or don't have any decent hypotheses to follow up, you can follow this process to systematically find the problem.<br /> <br /> Regarding the resolution to an incident: The resolution to any incident is usually one of two things:<br /> # Fix the underlying problem.<br /> # Fix the trigger itself.<br /> Fixing the trigger is relatively straightforward, but do make sure document in the thread what you changed to which trigger.<br /> Fixing the underlying problem can be more complex. A trade-off needs to be made sometimes between resolving technical debt, or simply patching the current system to resolve the issue. We usually look for a resolution that ensures that the problem won't re-occur soon, or makes it unexpected/unlikely for the problem to re-occur. Taking into account the time frame that is available to resolve the incident you can make some trade-offs. An example would be: normal backups of VMs are failing due to the Proxmox backup server being down/unreachable and it is determined that this cannot be resolved at that moment. We can set up automatic backups to local storage temporary to resolve the immediate problem and ensure we keep our SLO's versus setting up a new Proxmox Backup server at a different location. Since we don't have much time to resolve the problem, the resolution would be to set up the automatic backups to local storage, and set up a new Proxmox Backup Server later as a seperate issue.<br /> <br /> ===== Some known issues and their resolutions =====<br /> * SSH service is down: The internet is a vile place. There's constant port scanning and hacking attempts ongoing to any machine connected to the internet (mostly IPv4). Due to this, SSH has a throttling functionality build in to prevent a system from being DDOS'ed by the amount of malicious SSH requests. This throttling can cause the Zabbix server from being denied an SSH connection, of which several failures fire this trigger. This hypothesis can be proven with a `journalctl -u ssh | grep 'MaxStartups throttling'` (you probably want to select a relevant time period with `--since &quot;2 hours ago&quot;` or something similar to prevent having to process a month of logging). You can then compare the throttling start and end times with the timestamps of the item data itself. The resolution for the issue is to add our custom ssh configuration [https://chat.dsinternal.net/#narrow/stream/23-SRE---General/topic/DS.20Whitelisted.20Custom.20SSH.20configuration/near/1620 Custom SSH Configuration].<br /> * No backup for 3 days: Are S3 backup is very slow. Not much to prove as an underlying issue here. What needs to be done is check that the backup process is ongoing. The Zabbix latest data can be checked to verify that backups are running by checking that that days backups were done for the smaller buckets. The devteam email can be checked for if the backup process could not start on day due to it already running (it takes 24+ hours, and an attempt to start it is done each day by cron).<br /> * git.* HTTPS is down: On Sunday mostly, Gitlab gets automatically updated, but this incurs some downtime as the service is restarted. This is usually short enough to not be reported to Zulip as per our settings, but sometimes it's longer. If the service does not stay down, the issue can be just resolved.<br /> <br /> ==== Resolve incident + cleanup ====<br /> When you've executed and verified the resolution in the previous steps we can proceed resolving the issue in our Mattermost integration. Resolving an incident can be done by doing the following:<br /> # Verify that the trigger is no longer firing. An incident will be immediately re-opened if the trigger is still firing, and the incident cannot be considered resolved if the trigger is still firing. If the trigger is still firing but you're sure that you've resolved the problem, you might need to force the item the trigger depends on to update. This can be done by finding the item in the host's configuration on Zabbix and selecting 'Execute Now', after a short period this should force Zabbix to re-execute the item. You can check the timestamps in the latest data of an item to check if it was updated.<br /> # Close the incident by marking the topic as resolved, when there are no other triggers firing for the host.<br /> <br /> Unfortunately, some problems cause multiple critical and non-critical triggers to fire. This means we have to check Zabbix and Zulip for other fired triggers and ongoing incidents. The goal is to identify critical and non-critical incidents that were caused by the incident/underlying issue you just resolved.<br /> # First, these incidents need to be acknowledged on Zabbix, and in the acknowledgement message you mention the incident/problem that caused this.<br /> # Next, check the incident tracked by the integration on Mattermost using the `?ongoing` command. Resolve incidents that were (re-)opened by this incident by executing the following steps. If the first two fail (problem still persists, trigger is still firing), the incident needs to considered it's own issue and the relevant process needs to be followed (critical or non-critical depending on criticality).<br /> ## Ensuring the mentioned problem is no longer observable<br /> ## The trigger has resolved (You might need to force an update with `Execute Now`).<br /> ## Posting a link to the main incident you resolved with the comment that the underlying problem was resolved in that topic.<br /> ## Closing the incident by marking the topic as resolved, when there are no other triggers firing for the host.<br /> <br /> When you are done, there should be no more critical triggers firing in Zabbix or open in the Zabbix-Mattermost integration, for which no-one has taken responsibility or you have taken responsibility for and are not actively handling.<br /> <br /> ===Additional context===<br /> * Critical incidents are posted in [https://chat.dsinternal.net/#narrow/stream/24-SRE-.23-Critical '''SLA - Critical'''].<br /> * &lt;s&gt;When it is being tracked on GitLab a heavy check mark is added to the message.&lt;/s&gt;<br /> * &lt;s&gt;Responses on the thread and on GitLab are automatically synced (to some extend)&lt;/s&gt;<br /> * &lt;s&gt;When you reply with '''I agree that this has been fully resolved''' eventually our Zabbix-Mattermost integration will pick this up and a green check mark is added to the message.&lt;/s&gt;<br /> <br /> == Non-Critical incidents ==<br /> * Non-critical incidents are acknowledged within 9 hours and resolved within one week.<br /> <br /> === Acknowledging ===<br /> Fully acknowledging a non-critical incident requires the following tasks to have been completed:<br /> * Acknowledging the incident on Zabbix, which means you take responsibility of completing the steps listed below.<br /> <br /> <br /> The next steps don't have to be done immediately, as they have dependencies, but be started and scheduled for completion the next work day.<br /> <br /> Check if there's already a uncompleted milestone for this host with this issue in the metrics sheet.<br /> If a milestone is already present:<br /> * Report in the topic the Lynx project ID for resolving this issue.<br /> * If the ID has already been reported in the topic, we don't want to report it again and again, instead add the 🔁 emoji (:repeat:) under the zabbix bot alert<br /> <br /> If a milestone is NOT already present:<br /> * Add the non-critical incident as a milestone in the metrics sheet, following the naming convention<br /> ** Start date is the date of the incident<br /> ** DoD states what needs to be true for the non-critical incident to be consider resolved<br /> * Add the non-critical incident to Lynx as a project<br /> ** Follow the naming convention below for the title &amp; project ID<br /> ** Tasks need to be added<br /> ** Final tasks needs to have the SLO deadline set as 'constraint'<br /> ** Project priority is set to 99 while not estimated yet. After the estimation is done, the priority should be set to 20<br /> ** The tasks are estimated for SP<br /> * The Lynx project ID is reported in the non-critical incident's topic on Zulip, and logged in the metrics sheet<br /> * A Kimai activity is created in Kimai for the non-critical incident, following the naming convetion<br /> <br /> ==== Naming convention ====<br /> * Kimai activity name needs to follow the pattern: '&lt;YYYY-MM&gt; &lt;problem_title&gt;'. For &lt;problem_title&gt;, incorporate the trigger title and hostname for clarity.<br /> * Milestone name needs to follow the pattern: 'Delft Solutions Hosting Incident response work &lt;kimai_activity_name&gt;'<br /> * Lynx project name needs to follow the pattern: 'Delft Solutions Hosting Incident response work &lt;kimai_activity_name&gt;'<br /> * Lynx project ID needs to follow the pattern: 'SRE&lt;YYMM&gt;&lt;XXX&gt;', where &lt;XXX&gt; is some three letter shorthand that relates to the problem/host<br /> <br /> == Informational incidents ==<br /> * Informational incidents are acknowledged within 72 hours<br /> <br /> Checklist<br /> # Acknowledge on Zabbix<br /> # Sanity check the event, post result in thread<br /> # If action needed, perform action<br /> <br /> == If an incident is reported by other means than the Zabbix-Zulip integration ==<br /> Besides the automated Zabbix-Zulip integration, incidents can also be reported through emails from cron jobs, direct emails from customers, or topics in SRE General (such as alerts about Zulip updates or issues raised by colleagues), etc.<br /> # Acknowledge receipt.<br /> # Classify the incident as critical, non-critical, or informational.<br /> # Create an topic in the relevant SRE channel, stating the problem and that you is responsible for resolving it.<br /> # Proceed to treat the incident according to the criticality you just classified it as. (So for a critical incident, it means you now start the critical incident handling process)<br /> <br /> == Handover ==<br /> When handing over the responsibility of '''first responder''' (FR), the following needs to happen:<br /> * The handover can be initiated by both the upcoming FR or the acting FR<br /> * Acting FR adds the upcoming FR to the IPA sla-first-responder user group and enables Zabbix calling for the upcoming FR if they have that set by going to Zabbix &gt; Configuration &gt; Actions &gt; [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]<br /> * Before the handover, the acting FR must ensure that all active incidents are acknowledged (this includes alert emails or opened topics in SRE General, etc...), updated with the latest status, and properly documented.<br /> * The upcoming FR makes sure they are aware of the state of the SLA and knows what questions they wants to ask the acting FR.<br /> * The upcoming FR makes sure they are subscribed to the right channels.<br /> <br /> The following steps can be done async or in person:<br /> * The acting FR announces/informs the upcoming FR has been added to the sla-first-responder group (In Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] if asynq).<br /> * If the acting FR wants to hand over responsibility for any ongoing incident they also state which incidents they want the upcoming FR to take over.<br /> * If there are any particularities the upcoming FR needs to be aware of, those are shared.<br /> * The upcoming FR asks their questions until they are satisfied and able to take over the FR<br /> * The upcoming FR ensures they are subscribed to the following channels on Zulip: [https://chat.dsinternal.net/#narrow/stream/23-SRE---General SRE - General], [https://chat.dsinternal.net/#narrow/stream/24-SRE-.23-Critical SRE # Critical] and if part of the SRE team [https://chat.dsinternal.net/#streams/4/SRE%20##%20Non-critical SRE ## Non-Critical] and [https://chat.dsinternal.net/#streams/5/SRE%20###%20Informational SRE ### Informational].<br /> * The upcoming FR announces/informs that they are now the acting FR over Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel]<br /> * The now acting FR removes the previous FR from IPA the sla-first-responder user group and disables Zabbix calling for the previous FR if they had that enabled by going to Zabbix &gt; Configuration &gt; Actions &gt; [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_bonus&diff=254 2024-04-02T12:26:20Z

<p>Vincent: </p> <hr /> <div>== Calculating bonus ==<br /> <br /> # Obtain the bonus calculation template from 'Money' channel<br /> # Use steps from help tab to fill in the sheet<br /> # Save file as '&lt;year&gt;-Q&lt;quarter&gt;-bonus.xlsx' and export as pdf<br /> # Post pdf version of file in 'Money' channel<br /> <br /> == Create bonus booking on exact ==<br /> <br /> # Exact<br /> # Financieel<br /> # Boeken en grootboekrekeningen<br /> # Boekingen<br /> # Aanmaken<br /> # Click '91 - Bonus verdeling'<br /> # First line item<br /> ## Set 'Datum' to last day of the quarter you're booking the bonus for (e.g. December 31st when booking Q4 bonus)<br /> ## Set 'Grootboekrekening' to '4010 - Bijzondere beloning'<br /> ## Set 'Omschrijving' to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt;'<br /> ## Set 'Debet' to total bonus to be paid out as calculated in sheet (under 'Bonus costs')<br /> # Line item for every employee that receives a bonus (as calculated in bonus sheet)<br /> ## Set 'Datum' to same value as first line<br /> ## Set 'Grootboekrekening' to '1790 - Te betalen bonussen'<br /> ## Set 'Omschrijving to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt; &lt;employee name&gt;'<br /> ## Set 'Credit' to amount of bonus for that employee (as calculated in bonus sheet)<br /> # Line item for every owner that receives a bonus (as calculated in bonus sheet)<br /> ## Set 'Datum' to same value as first line<br /> ## Set 'Grootboekrekening' to '4010 - Bijzondere beloning'<br /> ## Set 'Omschrijving to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt; &lt;owner name&gt;'<br /> ## Set 'Credit' to amount of bonus for that owner (as calculated in bonus sheet)<br /> # If at this point there is a small difference between Debet and Credit (and all entered numbers are correct), you can create a line with Grootboekrekening '9200 - Rekenverschillen' to make up for the difference<br /> <br /> == Attach bonus calc sheet to booking in Exact ==<br /> <br /> # Exact<br /> # Documenten<br /> # Nieuw document<br /> # Subject: 'Bonus &lt;year&gt;-Q&lt;quarter&gt;'<br /> # Categorie: 'Crediteuren'<br /> # Date: Today<br /> # Delen: Huidige administratie<br /> # Type: Bijlage<br /> # Boeking: The bonus booking for that quarter<br /> # Attach the pdf version of the bonus calc sheet</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_bonus&diff=236 2024-03-05T15:26:46Z

<p>Vincent: /* Attach bonus calc sheet to booking in Exact */</p> <hr /> <div>== Calculating bonus ==<br /> <br /> # Obtain the bonus calculation template from 'Money' channel<br /> # Use steps from help tab to fill in the sheet<br /> # Save file as '&lt;year&gt;-Q&lt;quarter&gt;-bonus.xlsx' and export as pdf<br /> # Post pdf version of file in 'Money' channel<br /> <br /> == Create bonus booking on exact ==<br /> <br /> # Exact<br /> # Financieel<br /> # Boeken en grootboekrekeningen<br /> # Boekingen<br /> # Aanmaken<br /> # Click '91 - Bonus verdeling'<br /> # First line item<br /> ## Set 'Datum' to last day of the quarter you're booking the bonus for (e.g. December 31st when booking Q4 bonus)<br /> ## Set 'Grootboekrekening' to '4010 - Bijzondere beloning'<br /> ## Set 'Omschrijving' to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt;'<br /> ## Set 'Debet' to total bonus to be paid out as calculated in sheet (under 'Bonus costs')<br /> # Line item for every employee that receives a bonus (as calculated in bonus sheet)<br /> ## Set 'Datum' to same value as first line<br /> ## Set 'Grootboekrekening' to '1790 - Te betalen bonussen'<br /> ## Set 'Omschrijving to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt; &lt;employee name&gt;'<br /> ## Set 'Credit' to amount of bonus for that employee (as calculated in bonus sheet)<br /> # Line item for every owner that receives a bonus (as calculated in bonus sheet)<br /> ## Set 'Datum' to same value as first line<br /> ## Set 'Grootboekrekening' to '4010 - Bijzondere beloning'<br /> ## Set 'Omschrijving to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt; &lt;owner name&gt;'<br /> ## Set 'Credit' to amount of bonus for that employee (as calculated in bonus sheet)<br /> # If at this point there is a small difference between Debet and Credit (and all entered numbers are correct), you can create a line with Grootboekrekening '9200 - Rekenverschillen' to make up for the difference<br /> <br /> == Attach bonus calc sheet to booking in Exact ==<br /> <br /> # Exact<br /> # Documenten<br /> # Nieuw document<br /> # Subject: 'Bonus &lt;year&gt;-Q&lt;quarter&gt;'<br /> # Categorie: 'Crediteuren'<br /> # Date: Today<br /> # Delen: Huidige administratie<br /> # Type: Bijlage<br /> # Boeking: The bonus booking for that quarter<br /> # Attach the pdf version of the bonus calc sheet</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_bonus&diff=235 2024-03-05T15:26:22Z

<p>Vincent: Created page with &quot;== Calculating bonus == # Obtain the bonus calculation template from &#039;Money&#039; channel # Use steps from help tab to fill in the sheet # Save file as &#039;&lt;year&gt;-Q&lt;quarter&gt;-bonus.xlsx&#039; and export as pdf # Post pdf version of file in &#039;Money&#039; channel == Create bonus booking on exact == # Exact # Financieel # Boeken en grootboekrekeningen # Boekingen # Aanmaken # Click &#039;91 - Bonus verdeling&#039; # First line item ## Set &#039;Datum&#039; to last day of the quarter you&#039;re booking the bonus fo...&quot;</p> <hr /> <div>== Calculating bonus ==<br /> <br /> # Obtain the bonus calculation template from 'Money' channel<br /> # Use steps from help tab to fill in the sheet<br /> # Save file as '&lt;year&gt;-Q&lt;quarter&gt;-bonus.xlsx' and export as pdf<br /> # Post pdf version of file in 'Money' channel<br /> <br /> == Create bonus booking on exact ==<br /> <br /> # Exact<br /> # Financieel<br /> # Boeken en grootboekrekeningen<br /> # Boekingen<br /> # Aanmaken<br /> # Click '91 - Bonus verdeling'<br /> # First line item<br /> ## Set 'Datum' to last day of the quarter you're booking the bonus for (e.g. December 31st when booking Q4 bonus)<br /> ## Set 'Grootboekrekening' to '4010 - Bijzondere beloning'<br /> ## Set 'Omschrijving' to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt;'<br /> ## Set 'Debet' to total bonus to be paid out as calculated in sheet (under 'Bonus costs')<br /> # Line item for every employee that receives a bonus (as calculated in bonus sheet)<br /> ## Set 'Datum' to same value as first line<br /> ## Set 'Grootboekrekening' to '1790 - Te betalen bonussen'<br /> ## Set 'Omschrijving to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt; &lt;employee name&gt;'<br /> ## Set 'Credit' to amount of bonus for that employee (as calculated in bonus sheet)<br /> # Line item for every owner that receives a bonus (as calculated in bonus sheet)<br /> ## Set 'Datum' to same value as first line<br /> ## Set 'Grootboekrekening' to '4010 - Bijzondere beloning'<br /> ## Set 'Omschrijving to 'Bonuskosten &lt;year&gt; Q&lt;quarter&gt; &lt;owner name&gt;'<br /> ## Set 'Credit' to amount of bonus for that employee (as calculated in bonus sheet)<br /> # If at this point there is a small difference between Debet and Credit (and all entered numbers are correct), you can create a line with Grootboekrekening '9200 - Rekenverschillen' to make up for the difference<br /> <br /> == Attach bonus calc sheet to booking in Exact ==<br /> <br /> # Exact<br /> # Documenten<br /> # Nieuw document<br /> # Subject: 'Bonus &lt;year&gt;-Q&lt;quarter&gt;'<br /> # Categorie: 'Crediteuren'<br /> # Date: Today<br /> # Delen: Huidige administratie<br /> # Type: Bijlage<br /> # Boeking: The bonus booking for that quarter<br /> # Attach the pdf version of the bonux calc sheet</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=234 2024-03-05T14:27:44Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking bonus|Booking bonus]]<br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> * [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> * Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]<br /> * [[border reboot|Reboot border without downtime]]<br /> * [[WS Proxmox node reboot|Reboot WS Proxmox node without downtime]]<br /> <br /> == Other ==<br /> <br /> * [[standard tools|Standard Tools]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=233 2024-03-04T10:02:58Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> * [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> * Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]<br /> * [[border reboot|Reboot border without downtime]]<br /> * [[WS Proxmox node reboot|Reboot WS Proxmox node without downtime]]<br /> <br /> == Other ==<br /> <br /> * [[standard tools|Standard Tools]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=232 2024-03-04T09:47:51Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[bonus calculation|Bonus calculation]]<br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> * [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> * Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]<br /> * [[border reboot|Reboot border without downtime]]<br /> * [[WS Proxmox node reboot|Reboot WS Proxmox node without downtime]]<br /> <br /> == Other ==<br /> <br /> * [[standard tools|Standard Tools]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Border_reboot&diff=219 2024-02-19T15:21:13Z

<p>Vincent: </p> <hr /> <div>Note: Throughout this guide &lt;ipv4&gt; and &lt;ipv6&gt; are to be replaced by the correct IP's.<br /> <br /> == Preflight checks ==<br /> These checks are to be done on the other border (So the border that will stay online). The commands are to be invoked in `vtysh`.<br /> * Confirm our IPv4 block is announced over BGP with `show ip bgp neighbors &lt;ipv4&gt; advertised-routes`<br /> * Confirm our IPv6 block is announced over BGP with `show bgp neighbors &lt;ipv6&gt; advertised-routes`<br /> * Confirm that the border receives the ROUTED IPv4 routes from the router with `show ip route`<br /> * Confirm that the border received the ROUTED &amp; LAN IPv6 routes from the router with `show ipv6 route`<br /> <br /> Set a maintenance period for the host on Zabbix<br /> <br /> == Disabling routing through a border ==<br /> On a border in `vtysh`, update the running configuration by invoking the following:<br /> <br /> * config<br /> * router bgp<br /> * neighbor &lt;ipv4&gt; shutdown<br /> * neighbor &lt;ipv6&gt; shutdown<br /> * exit<br /> * router ospf<br /> * no default-information originate<br /> * exit<br /> * router ospf6<br /> * no default-information originate<br /> * exit<br /> * exit<br /> <br /> == Reboot the border ==<br /> <br /> * After performing the pre-flight checks and disabling the routing, you can choose to wait until traffic has decreased (e.g. using `bmon` to check bandwidth used on interfaces)<br /> * Execute `reboot` command<br /> * When the border is back online, execute relavant items (system uptime, operating system, reboot required) to ensure these will not activate a trigger after disabling maintenance mode<br /> * If you do not expect any Zabbix alert related to the reboot to be fired, delete the maintenance period<br /> <br /> == Troubleshooting ==<br /> <br /> Undoing the shutdown of the neighbors can be done by invoking `no neighbor &lt;ipv4&gt;/&lt;ipv6&gt; shutdown` in the `router bgp` part of the configuration.<br /> <br /> And the `no default-information originate` can be undone by invoking `default-information originate` in the corect ospf part of the configuration (ospf or ospf6, depending on which one you wish to re-enable).<br /> <br /> A reload/restart of the service will also reset to normal configuration.</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Border_reboot&diff=218 2024-02-19T14:43:26Z

<p>Vincent: /* Reboot the border */</p> <hr /> <div>Note: Throughout this guide &lt;ipv4&gt; and &lt;ipv6&gt; are to be replaced by the correct IP's.<br /> <br /> == Preflight checks ==<br /> These checks are to be done on the other border (So the border that will stay online). The commands are to be invoked in `vtysh`.<br /> * Confirm our IPv4 block is announced over BGP with `show ip bgp neighbors &lt;ipv4&gt; advertised-routes`<br /> * Confirm our IPv6 block is announced over BGP with `show bgp neighbors &lt;ipv6&gt; advertised-routes`<br /> * Confirm that the border receives the ROUTED IPv4 routes from the router with `show ip route`<br /> * Confirm that the border received the ROUTED &amp; LAN IPv6 routes from the router with `show ipv6 route`<br /> <br /> == Disabling routing through a border ==<br /> On a border in `vtysh`, update the running configuration by invoking the following:<br /> <br /> * config<br /> * router bgp<br /> * neighbor &lt;ipv4&gt; shutdown<br /> * neighbor &lt;ipv6&gt; shutdown<br /> * exit<br /> * router ospf<br /> * no default-information originate<br /> * exit<br /> * router ospf6<br /> * no default-information originate<br /> * exit<br /> * exit<br /> <br /> == Reboot the border ==<br /> <br /> After performing the pre-flight checks and disabling the routing, you can choose to wait until traffic has decreased (e.g. using `bmon` to check bandwidth used on interfaces)<br /> <br /> Execute `reboot` command<br /> <br /> == Troubleshooting ==<br /> <br /> Undoing the shutdown of the neighbors can be done by invoking `no neighbor &lt;ipv4&gt;/&lt;ipv6&gt; shutdown` in the `router bgp` part of the configuration.<br /> <br /> And the `no default-information originate` can be undone by invoking `default-information originate` in the corect ospf part of the configuration (ospf or ospf6, depending on which one you wish to re-enable).<br /> <br /> A reload/restart of the service will also reset to normal configuration.</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Border_reboot&diff=217 2024-02-19T14:38:56Z

<p>Vincent: </p> <hr /> <div>Note: Throughout this guide &lt;ipv4&gt; and &lt;ipv6&gt; are to be replaced by the correct IP's.<br /> <br /> == Preflight checks ==<br /> These checks are to be done on the other border (So the border that will stay online). The commands are to be invoked in `vtysh`.<br /> * Confirm our IPv4 block is announced over BGP with `show ip bgp neighbors &lt;ipv4&gt; advertised-routes`<br /> * Confirm our IPv6 block is announced over BGP with `show bgp neighbors &lt;ipv6&gt; advertised-routes`<br /> * Confirm that the border receives the ROUTED IPv4 routes from the router with `show ip route`<br /> * Confirm that the border received the ROUTED &amp; LAN IPv6 routes from the router with `show ipv6 route`<br /> <br /> == Disabling routing through a border ==<br /> On a border in `vtysh`, update the running configuration by invoking the following:<br /> <br /> * config<br /> * router bgp<br /> * neighbor &lt;ipv4&gt; shutdown<br /> * neighbor &lt;ipv6&gt; shutdown<br /> * exit<br /> * router ospf<br /> * no default-information originate<br /> * exit<br /> * router ospf6<br /> * no default-information originate<br /> * exit<br /> * exit<br /> <br /> == Reboot the border ==<br /> <br /> Execute `reboot` command<br /> <br /> == Troubleshooting ==<br /> <br /> Undoing the shutdown of the neighbors can be done by invoking `no neighbor &lt;ipv4&gt;/&lt;ipv6&gt; shutdown` in the `router bgp` part of the configuration.<br /> <br /> And the `no default-information originate` can be undone by invoking `default-information originate` in the corect ospf part of the configuration (ospf or ospf6, depending on which one you wish to re-enable).<br /> <br /> A reload/restart of the service will also reset to normal configuration.</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Payment_reminders&diff=209 2024-01-16T13:58:21Z

<p>Vincent: Created page with &quot;# Log in to Exact # On the main Exact page go to &quot;Verkoop&quot; &gt; &quot;Openstaande posten&quot; &gt; &quot;Herinneringen afdrukken&quot; # Select the invoice for which you want to send a reminder and click &quot;Email&quot; (If you want Exact to send the email) or &quot;Afdrukken&quot; (If you want to generate a pdf that you can email yourself) # Select the correct Template, verify this is what you want and send # When returning to the overview page you will now see a link to view sent reminders for this invoice&quot;</p> <hr /> <div># Log in to Exact<br /> # On the main Exact page go to &quot;Verkoop&quot; &gt; &quot;Openstaande posten&quot; &gt; &quot;Herinneringen afdrukken&quot;<br /> # Select the invoice for which you want to send a reminder and click &quot;Email&quot; (If you want Exact to send the email) or &quot;Afdrukken&quot; (If you want to generate a pdf that you can email yourself)<br /> # Select the correct Template, verify this is what you want and send<br /> # When returning to the overview page you will now see a link to view sent reminders for this invoice</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=208 2024-01-16T13:55:46Z

<p>Vincent: /* Exact */</p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> * [[payment reminders|Send payment reminder]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Booking_wages&diff=207 2023-12-22T15:17:46Z

<p>Vincent: </p> <hr /> <div>== Wage slips ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (wage slip)<br /> # Beschijving: Salaris periode {YEAR}-{MONTH}-M / {YEAR}-{MONTH}-M {NAME}, Periode: M<br /> # Totaalbedrag: '''Totaal netto'''<br /> # Line items:<br /> ## '''Bruto &gt; Salaris''' as '''Loon (4000)''',<br /> ## '''Bruto &gt; Bonus (BT)''' as '''Te betalen bonussen (1790)'''<br /> ## '''Loonheffing''' as '''af te dragen loonheffing (1700)'''<br /> ## '''Netto &gt; Onkostenvergoeding''' as '''Kosten nettovergoedingen'''<br /> <br /> == Wage taxes ==<br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (LH)<br /> # Beschrijving: {LHnummer en volgnummer}, Periode: D<br /> ## '''Loonbelasting / premie volksverzekering''' as '''Af te dragen loonheffing (1700)'''<br /> ## '''Premies''' as '''Kosten sociale premies werkgever (4041)'''<br /> <br /> == Pension ==<br /> <br /> # Exact<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Boekingen &gt; Aanmaken<br /> # Inkoop &gt; '''80 - Salarisstroken'''<br /> # Add file (JP)<br /> # Beschrijving: Pensioen {YEAR}-{MONTH}-M, Periode: IN<br /> # Totaalbedrag: '''Amount under pensions on JP'''<br /> # Line items:<br /> ## For each person who received pension payment: '''Pensioenen (4011)'''<br /> <br /> == Reconciliation (after payment) ==<br /> # Financieel &gt; Boekingen en grootboekrekeningen &gt; Overzichten &gt; Kaarten<br /> # Search for '''Af te dragen loonheffing (1700)'''<br /> # Mark the wage slips together with the IRS slip for wage taxes. The difference at the bottom (e.g. 0.16 EUR) needs to be added to the wage tax document.<br /> ## '''Af te dragen loonheffing (1700)''' 0.16 EUR<br /> ## '''Rekenverschillen (9200)''' -0.16 EUR<br /> ## Repeat process; difference should now be 0<br /> # Afletteren; difference should be 0</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Incident_Handling&diff=203 2023-08-04T14:13:49Z

<p>Vincent: </p> <hr /> <div>== Critical incidents ==<br /> * Critical incidents are resolved within 16 hours.<br /> <br /> Checklist<br /> # Acknowledge on Zabbix and state who is responsible for resolving this in the description<br /> # Determine affected clients<br /> # Communicate to affected clients that the issue is being investigated<br /> # Communicate plan/next steps (even if that is gathering information)<br /> # Communicate findings/results of executed plan, go back to previous step if not resolved<br /> # Resolve incident<br /> <br /> == Non-Critical incidents ==<br /> * Non-critical incidents are acknowledged within 9 hours and resolved within one week.<br /> <br /> Checklist<br /> # Acknowledge on Zabbix and state who is responsible for resolving this in the description<br /> # Communicate plan/next steps (even if that is gathering information)<br /> # Communicate findings/results of executed plan, go back to previous step if not resolved<br /> # Resolve incident<br /> <br /> == Informational incidents ==<br /> * Informational incidents are acknowledged within 72 hours<br /> <br /> Checklist<br /> # Acknowledge on Zabbix<br /> # Sanity check the event, post result in thread<br /> # If action needed, perform action</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Incident_Handling&diff=202 2023-08-04T14:12:58Z

<p>Vincent: </p> <hr /> <div>== Critical incidents ==<br /> * Critical incidents are resolved within 16 hours.<br /> <br /> Checklist<br /> # Acknowledge on Zabbix and state who is responsible for resolving this in the description<br /> # Determine affected clients<br /> # Communicate to affected clients that the issue is being investigated<br /> # Communicate plan/next steps (even if that is gathering information)<br /> # Communicate findings/results of executed plan, go back to previous step if not resolved<br /> # Resolve incident<br /> <br /> == Non-Critical incidents ==<br /> * Non-critical incidents are acknowledged within 9 hours and resolved within one week.<br /> <br /> Checklist<br /> # Acknowledge on Zabbix and state who is responsible for resolving this in the description<br /> # Communicate plan/next steps (even if that is gathering information)<br /> # Communicate findings/results of executed plan, go back to previous step if not resolved<br /> # Resolve incident<br /> <br /> == Informational incidents ==<br /> * Informational incidents are acknowledged within 72 hours<br /> <br /> Checklist<br /> # Acknowledge on Zabbix<br /> # Sanity check the event, post result in thread</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Create_gitlab_runner_host&diff=190 2023-05-16T13:38:59Z

<p>Vincent: </p> <hr /> <div># Create a (Debian) host<br /> # [https://docs.docker.com/engine/install/debian/ Install Docker Engine on Debian]<br /> # [https://docs.gitlab.com/runner/install/linux-repository.html Install GitLab runner]<br /> # [https://docs.gitlab.com/runner/register/ Register runner]<br /> ## If you want to run Code Quality jobs on the runner [https://docs.gitlab.com/ee/ci/testing/code_quality.html#improve-code-quality-performance-with-private-runners see this guide]<br /> <br /> Coming soon (tm):<br /> # [https://git.dsinternal.net/delft-solutions/infrastructure/debian-ds-gitlab-runner Install ds-gitlab-runner]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=189 2023-05-16T12:42:59Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]<br /> * [[vm setup|Create a (Debian) VM]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Create_gitlab_runner_host&diff=188 2023-05-16T12:40:33Z

<p>Vincent: </p> <hr /> <div># Create a (Debian) host<br /> # [https://docs.docker.com/engine/install/debian/ Install Docker Engine on Debian]<br /> # [https://docs.gitlab.com/runner/install/linux-repository.html Install GitLab runner]<br /> # Register runner<br /> ## If you want to run Code Quality jobs on the runner [https://docs.gitlab.com/ee/ci/testing/code_quality.html#improve-code-quality-performance-with-private-runners see this guide]<br /> <br /> Coming soon (tm):<br /> # [https://git.dsinternal.net/delft-solutions/infrastructure/debian-ds-gitlab-runner Install ds-gitlab-runner]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Create_gitlab_runner_host&diff=187 2023-05-16T12:38:33Z

<p>Vincent: </p> <hr /> <div># Create a (Debian) host<br /> # [https://docs.docker.com/engine/install/debian/ Install Docker Engine on Debian]<br /> # [https://docs.gitlab.com/runner/install/linux-repository.html Install GitLab runner]<br /> # Register runner<br /> <br /> Coming soon (tm):<br /> # [https://git.dsinternal.net/delft-solutions/infrastructure/debian-ds-gitlab-runner Install ds-gitlab-runner]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Create_gitlab_runner_host&diff=186 2023-05-16T08:55:45Z

<p>Vincent: </p> <hr /> <div># [https://docs.docker.com/engine/install/debian/ Install Docker Engine on Debian]<br /> # [https://docs.gitlab.com/runner/install/linux-repository.html Install GitLab runner]<br /> # Register runner<br /> <br /> Coming soon (tm):<br /> # [https://git.dsinternal.net/delft-solutions/infrastructure/debian-ds-gitlab-runner Install ds-gitlab-runner]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=184 2023-05-08T09:22:51Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=183 2023-05-08T09:22:40Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> * [[invoicing|Send an invoice}}<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Create_gitlab_runner_host&diff=182 2023-04-25T14:58:04Z

<p>Vincent: Created page with &quot;# [https://docs.docker.com/engine/install/debian/ Install Docker Engine on Debian] # [https://docs.gitlab.com/runner/install/linux-repository.html Install GitLab runner] # [https://git.dsinternal.net/delft-solutions/infrastructure/debian-ds-gitlab-runner Install ds-gitlab-runner]&quot;</p> <hr /> <div># [https://docs.docker.com/engine/install/debian/ Install Docker Engine on Debian]<br /> # [https://docs.gitlab.com/runner/install/linux-repository.html Install GitLab runner]<br /> # [https://git.dsinternal.net/delft-solutions/infrastructure/debian-ds-gitlab-runner Install ds-gitlab-runner]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=181 2023-04-25T14:52:56Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be further populated with guide from drive''<br /> * [[create gitlab runner host|Create a GitLab runner host]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=180 2023-04-25T10:55:11Z

<p>Vincent: </p> <hr /> <div>== Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == SRE ==<br /> <br /> ''To be populated with guide from drive''</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=179 2023-04-25T10:01:26Z

<p>Vincent: </p> <hr /> <div>== Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]<br /> <br /> == SRE ==<br /> <br /> ''To be populated with guide from drive''</div>

Vincent https://docs.delftsolutions.nl/index.php?title=New_receipt&diff=178 2023-04-25T09:57:10Z

<p>Vincent: </p> <hr /> <div># Log into Exact<br /> # Go to “Purchase” &gt; “Entries” &gt; “Overview”<br /> # Click “New”<br /> # Click “60 - Inkoopboek”<br /> # Add a picture of the receipt as an attachment<br /> # Under “Supplier”, find the supplier and select the correct supplier<br /> # Numbered list item<br /> ## If the supplier does not exist, you have to add a new supplier, but there is no guide for this<br /> # Under “Invoice Data”<br /> ## Enter the description of what is on the receipt (e.g. enter “lunch stuff” for when you have a receipt for buying lunch stuff)<br /> ## Enter total amount on the receipt under “Total amount” <br /> ## Update “Invoice Date” (And probably also “Due date”) to match the date on the receipt<br /> # Make sure the expenses are for the correct G/L Account, e.g. lunch/borrel stuff should be under 4012<br /> # Make sure the VAT code is correct, as well as the VAT amount<br /> # Click “Save + new”<br /> # Ask Vincent to reconcile the payment+receipt<br /> # Done</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Top_up_account&diff=177 2023-04-25T09:52:10Z

<p>Vincent: Created page with &quot;We preferably top up our expense accounts every month (or more frequently in case alerts come in on the “Money” channel on Mattermost) # Determine the amount needed to get your expense account back to €250 # Go to the Bunq “DevTeam” account # Select “Pay” # Enter amount previously determined # Click “Choose recipient” # Click “My accounts” # Select the correct expense account # Enter a reason for the top up (e.g. “top up after paying for car rent...&quot;</p> <hr /> <div>We preferably top up our expense accounts every month (or more frequently in case alerts come in on the “Money” channel on Mattermost)<br /> <br /> # Determine the amount needed to get your expense account back to €250<br /> # Go to the Bunq “DevTeam” account<br /> # Select “Pay”<br /> # Enter amount previously determined<br /> # Click “Choose recipient”<br /> # Click “My accounts”<br /> # Select the correct expense account<br /> # Enter a reason for the top up (e.g. “top up after paying for car rental” or “top up after paying for a lot of lunches”)<br /> # Review the payment details<br /> # Click “Send for approval”<br /> # Notify Vincent you created the top up request</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Internal&diff=176 2023-04-25T09:48:20Z

<p>Vincent: </p> <hr /> <div>== Projects ==<br /> <br /> Era Inventory [[project_era_inventory_api|API Description]]<br /> <br /> == Process ==<br /> <br /> [[definition of done|Definition of Done]]<br /> <br /> == Finance ==<br /> <br /> === Exact ===<br /> <br /> * [[booking wages|Booking wages]]<br /> * [[new receipt|Enter a new receipt]]<br /> * [[reconciliation|Reconciliation of transaction]]<br /> <br /> === Bunq ===<br /> <br /> * [[top up account|Top up expense account]]</div>

Vincent https://docs.delftsolutions.nl/index.php?title=File:Tompouce.jpg&diff=175 2023-04-24T15:07:33Z

<p>Vincent: </p> <hr /> <div></div>

Vincent https://docs.delftsolutions.nl/index.php?title=Reconciliation&diff=174 2023-04-24T15:06:22Z

<p>Vincent: </p> <hr /> <div>== Navigation ==<br /> The page for interacting with transactions to reconcile them can be found on Exact at: 'Financial' -&gt; 'Banking &amp; Cash' -&gt; 'To be completed'.<br /> <br /> == Retrieving Transactions ==<br /> [[File:Search panel for transactions to reconcile.png|thumb|Search panel for transactions to reconcile]]<br /> <br /> First, we need to retrieve any transaction which need reconciliation. For this we need to use the search panel. The following steps are required:<br /> <br /> * Make sure the checkbox for 'To be completed' is checked.<br /> * Ensure no range is set. Or if it is set, that the range includes the date the transaction you wish to reconcile was made.<br /> * Keep all other boxes and options empty.<br /> * Click 'Refresh' if you made any changes to the search panel after arriving on the page.<br /> <br /> On the right you can find an image showing an example of how the search panel ought to look.<br /> <br /> == Processing Transactions ==<br /> [[File:Transaction example.png|thumb|Example of a transaction that needs reconciliation]]<br /> <br /> To the right, you can find an example of a transaction that requires reconciliation. In order to do this, two steps are required:<br /> # Ensure the 'Entry line' is set correctly. This is the information in the middle block of the transaction overview.<br /> # Match the transaction to the correct invoice/receipt.<br /> <br /> We'll use the example transaction to demonstrate how to perform these steps.<br /> <br /> === Setting the Entry line ===<br /> [[File:Grootboekregel example.png|thumb|Example of setting the G/L Account]]<br /> <br /> Setting the Entry line correctly consists of two things.<br /> # Setting the correct G/L Account. this refers to the ledger this cost should be put on. This is ususually '1600 - Crediteuren'.<br /> # Setting the correct Account. This refers to the business relation that was involved in this transaction.<br /> <br /> In the example transaction, you see that the G/L Account is '1290 - Kruisposten liquide middelen' and the 'Account' is not set. Both parts are wrong for this transaction, so we need to set them correctly. There are two ways to achieve this:<br /> # By clicking the suggestion from Exact. This is the blueish rectangle below '1290- Kruisposten liquide middelen'. The values shown are the suggestions from Exact for the G/L Account (In this case '1600 - Crediteuren') and for the Account (In this case '40 - Albert heijn'). In this case, the suggestions are correct (For standard transactions, the '1600 - Crediteuren' is the correct G/L Account, and the payment was made to Albert Heijn, so the Account '40 - Albert Heijn' is also correct), but there might not always be a correct suggestion. There can also be multiple suggestions.<br /> # By clicking the 'Edit' button at the far right of the transaction line and manually adjusting the values.<br /> <br /> Both actions take you to 'Statement line' edit modal, of which an example can be seen to the right. If you used option 1, the G/L Account and Account textbox will be filled in with the information from the suggestion. If you used option 2, you need to manually enter the correct value in the textbox. You can either type the number, or the name of the G/L Account and/or Account. When typing, a box will appear with suggestions. Finally, select the matching option from the suggestions box. You can also double click on a textbox to get another modal with a list of all possible values, from which you can pick the correct one.<br /> <br /> Finally, click the 'Save' button at the top to store the updated values.<br /> <br /> Note: If the correct value for Account cannot be found in the list/suggestions, it is likely that the invoice/receipt for that transaction has not been added yet. Adding the receipt/invoice should be done first. This is because if you are using the Scan Service, the Account will be automaticly created and likely contain much more information then if you created the Account yourself. It's also a lot easier.<br /> <br /> === Matching the Transaction ===<br /> [[File:Example matching transaction and receipts-invoices modal.png|thumb|Example matching transaction and receipts/invoices modal]]<br /> <br /> With the Entry line set, we can move on to reconcile the transaction. To do this, click the 'Match' button to bring up the modal to select the invoices/receipts this transaction matches with. An example of the modal can be seen on the right.<br /> <br /> Exact uses the G/L Account and Account of the transaction to present you with a list of possible receipts/invoices that could be matched with the transaction. If the list in the modal is empty, it means that either the G/L Account and Account are not set correctly, or the invoice/receipt has not been entered into the system yet.<br /> <br /> To reconcile the transaction you need to take the following steps:<br /> # Check the checkboxes for the receipts/invoices that belong to this transaction. Generally, this means selecting the receipt/invoice with the matching monetary value.<br /> # Make sure that the drop down for 'Difference' is set to 'Don't write off' for the selected receipts/invoices.<br /> # Click 'Enter' to finish the reconciliation.<br /> <br /> Congratulations, you've just finished reconciling a transaction!</div>

Vincent https://docs.delftsolutions.nl/index.php?title=Reconciliation&diff=173 2023-04-24T15:06:11Z

<p>Vincent: </p> <hr /> <div>== Navigation ==<br /> The page for interacting with transactions to reconcile them can be found on Exact at: 'Financial' -&gt; 'Banking &amp; Cash' -&gt; 'To be completed'.<br /> <br /> == Retrieving Transactions ==<br /> [[File:Search panel for transactions to reconcile.png|thumb|Search panel for transactions to reconcile]]<br /> <br /> First, we need to retrieve any transaction which need reconciliation. For this we need to use the search panel. The following steps are required:<br /> <br /> * Make sure the checkbox for 'To be completed' is checked.<br /> * Ensure no range is set. Or if it is set, that the range includes the date the transaction you wish to reconcile was made.<br /> * Keep all other boxes and options empty.<br /> * Click 'Refresh' if you made any changes to the search panel after arriving on the page.<br /> <br /> On the right you can find an image showing an example of how the search panel ought to look.<br /> <br /> == Processing Transactions ==<br /> [[File:Transaction example.png|thumb|Example of a transaction that needs reconciliation]]<br /> <br /> To the right, you can find an example of a transaction that requires reconciliation. In order to do this, two steps are required:<br /> # Ensure the 'Entry line' is set correctly. This is the information in the middle block of the transaction overview.<br /> # Match the transaction to the correct invoice/receipt.<br /> <br /> We'll use the example transaction to demonstrate how to perform these steps.<br /> <br /> === Setting the Entry line ===<br /> [[File:Grootboekregel example.png|thumb|Example of setting the G/L Account]]<br /> <br /> Setting the Entry line correctly consists of two things.<br /> # Setting the correct G/L Account. this refers to the ledger this cost should be put on. This is ususually '1600 - Crediteuren'.<br /> # Setting the correct Account. This refers to the business relation that was involved in this transaction.<br /> <br /> In the example transaction, you see that the G/L Account is '1290 - Kruisposten liquide middelen' and the 'Account' is not set. Both parts are wrong for this transaction, so we need to set them correctly. There are two ways to achieve this:<br /> # By clicking the suggestion from Exact. This is the blueish rectangle below '1290- Kruisposten liquide middelen'. The values shown are the suggestions from Exact for the G/L Account (In this case '1600 - Crediteuren') and for the Account (In this case '40 - Albert heijn'). In this case, the suggestions are correct (For standard transactions, the '1600 - Crediteuren' is the correct G/L Account, and the payment was made to Albert Heijn, so the Account '40 - Albert Heijn' is also correct), but there might not always be a correct suggestion. There can also be multiple suggestions.<br /> # By clicking the 'Edit' button at the far right of the transaction line and manually adjusting the values.<br /> <br /> Both actions take you to 'Statement line' edit modal, of which an example can be seen to the right. If you used option 1, the G/L Account and Account textbox will be filled in with the information from the suggestion. If you used option 2, you need to manually enter the correct value in the textbox. You can either type the number, or the name of the G/L Account and/or Account. When typing, a box will appear with suggestions. Finally, select the matching option from the suggestions box. You can also double click on a textbox to get another modal with a list of all possible values, from which you can pick the correct one.<br /> <br /> Finally, click the 'Save' button at the top to store the updated values.<br /> <br /> Note: If the correct value for Account cannot be found in the list/suggestions, it is likely that the invoice/receipt for that transaction has not been added yet. Adding the receipt/invoice should be done first. This is because if you are using the Scan Service, the Account will be automaticly created and likely contain much more information then if you created the Account yourself. It's also a lot easier.<br /> <br /> === Matching the Transaction ===<br /> [[File:Example matching transaction and receipts-invoices modal.png|thumb|Example matching transaction and receipts/invoices modal]]<br /> <br /> With the Entry line set, we can move on to reconcile the transaction. To do this, click the 'Match' button to bring up the modal to select the invoices/receipts this transaction matches with. An example of the modal can be seen on the right.<br /> <br /> Exact uses the G/L Account and Account of the transaction to present you with a list of possible receipts/invoices that could be matched with the transaction. If the list in the modal is empty, it means that either the G/L Account and Account are not set correctly, or the invoice/receipt has not been entered into the system yet.<br /> <br /> To reconcile the transaction you need to take the following steps:<br /> # Check the checkboxes for the receipts/invoices that belong to this transaction. Generally, this means selecting the receipt/invoice with the matching monetary value.<br /> # Make sure that the drop down for 'Difference' is set to 'Don't write off' for the selected receipts/invoices.<br /> # Click 'Enter' to finish the reconciliation.<br /> <br /> ?????<br /> PROFIT<br /> Congratulations, you've just finished reconciling a transaction!</div>

Vincent https://docs.delftsolutions.nl/index.php?title=File:Prinspils.png&diff=172 2023-04-24T13:30:05Z

<p>Vincent: </p> <hr /> <div></div>

Vincent https://docs.delftsolutions.nl/index.php?title=New_receipt&diff=171 2023-04-24T13:26:24Z

<p>Vincent: </p> <hr /> <div># Log into Exact<br /> # Go to “Purchase” &gt; “Entries” &gt; “Overview”<br /> # Click “New”<br /> # Click “60 - Inkoopboek”<br /> # Add a picture of the receipt as an attachment<br /> # Under “Supplier”, find the supplier and select the correct supplier<br /> # Note: If the supplier does not exist, you have to add a new supplier, but there is no guide for this<br /> # Under “Invoice Data”<br /> # Enter the description of what is on the receipt (e.g. enter “lunch stuff” for when you have a receipt for buying lunch stuff)<br /> # Enter total amount on the receipt under “Total amount” <br /> # Update “Invoice Date” (And probably also “Due date”) to match the date on the receipt<br /> # Make sure the expenses are for the correct G/L Account, e.g. lunch/borrel stuff should be under 4012<br /> # Click “Save + new”<br /> # Ask Vincent to reconcile the payment+receipt<br /> # Done</div>

Vincent